Error in when backing up SQL

[BasigDegrasia3]

Hi All,

We have configured SQL backups in our environment. One of the client that we are trying tyo backup its database has a strange behavior, we we run the job via the activity monitor we gotr the error shown below, while when i run the created *.bch file used for backing up the database from client server SQL, the job completed successfully with out any error.

Hint, the account using have sysadmin rights to all databases?

Please Advbise.

1/14/2014 9:47:16 AM - Info nbjm(pid=5244) starting backup job (jobid=484798) for client sipc-lyncdb, policy lyncdb-Weekly-Full, schedule Full  

1/14/2014 9:47:16 AM - Info nbjm(pid=5244) requesting MEDIA_SERVER_WITH_ATTRIBUTES resources from RB for backup job (jobid=484798, request id:{2F7AC2B0-6F02-4870-B053-873E53EBCCB4})  

1/14/2014 9:47:16 AM - requesting resource STU2

1/14/2014 9:47:16 AM - requesting resource sipc-netbackup.NBU_CLIENT.MAXJOBS.sipc-lyncdb

1/14/2014 9:47:16 AM - requesting resource sipc-netbackup.NBU_POLICY.MAXJOBS.lyncdb-Weekly-Full

1/14/2014 9:47:16 AM - granted resource sipc-netbackup.NBU_CLIENT.MAXJOBS.sipc-lyncdb

1/14/2014 9:47:16 AM - granted resource sipc-netbackup.NBU_POLICY.MAXJOBS.lyncdb-Weekly-Full

1/14/2014 9:47:16 AM - granted resource sipc-sapdev2-hcart2-robot-tld-2

1/14/2014 9:47:16 AM - estimated 0 Kbytes needed

1/14/2014 9:47:16 AM - Info nbjm(pid=5244) started backup (backupid=sipc-lyncdb_1389682036) job for client sipc-lyncdb, policy lyncdb-Weekly-Full, schedule Full on storage unit sipc-sapdev2-hcart2-robot-tld-2

1/14/2014 9:47:24 AM - started process bpbrm (10120)

1/14/2014 9:47:26 AM - Info bpbrm(pid=10120) sipc-lyncdb is the host to backup data from     

1/14/2014 9:47:26 AM - Info bpbrm(pid=10120) reading file list from client        

1/14/2014 9:47:26 AM - connecting

1/14/2014 9:47:28 AM - Info bpbrm(pid=10120) starting bphdb on client         

1/14/2014 9:47:28 AM - Info bphdb(pid=4172) Backup started           

1/14/2014 9:47:28 AM - connected; connect time: 00:00:02

1/14/2014 9:47:35 AM - Info dbclient(pid=3668) DBMS MSG - ODBC return code <-1>, SQL State <08004>, SQL Message <916><[Microsoft][ODBC SQL Server Driver][SQL Server]The server principal "NT AUTHORITY\SYSTEM" is not able to access the database "LcsCDR" under the current security context.>.

1/14/2014 9:47:35 AM - Info dbclient(pid=3668) ERR - Error found executing <use "LcsCDR">.      

1/14/2014 9:47:35 AM - Info dbclient(pid=3668) ERR - Unable to determine FILESTREAM paths for database LcsCDR.   

1/14/2014 9:47:35 AM - Info dbclient(pid=3668) INF - OPERATION #1 of batch C:\Program Files\Veritas\NetBackup\DbExt\MsSql\F.bch FAILED with STATUS 1 (0 is normal). Elapsed time = 4(4) seconds.

1/14/2014 9:47:39 AM - Info dbclient(pid=3668) DBMS MSG - ODBC return code <-1>, SQL State <08004>, SQL Message <916><[Microsoft][ODBC SQL Server Driver][SQL Server]The server principal "NT AUTHORITY\SYSTEM" is not able to access the database "mgc" under the current security context.>.

1/14/2014 9:47:39 AM - Info dbclient(pid=3668) ERR - Error found executing <use "mgc">.      

1/14/2014 9:47:40 AM - Info dbclient(pid=3668) ERR - Unable to determine FILESTREAM paths for database mgc.   

1/14/2014 9:47:40 AM - Info dbclient(pid=3668) INF - OPERATION #2 of batch C:\Program Files\Veritas\NetBackup\DbExt\MsSql\F.bch FAILED with STATUS 1 (0 is normal). Elapsed time = 2(2) seconds.

1/14/2014 9:47:44 AM - Info dbclient(pid=3668) DBMS MSG - ODBC return code <-1>, SQL State <08004>, SQL Message <916><[Microsoft][ODBC SQL Server Driver][SQL Server]The server principal "NT AUTHORITY\SYSTEM" is not able to access the database "QoEMetrics" under the current security context.>.

1/14/2014 9:47:44 AM - Info dbclient(pid=3668) ERR - Error found executing <use "QoEMetrics">.      

1/14/2014 9:47:44 AM - Info dbclient(pid=3668) ERR - Unable to determine FILESTREAM paths for database QoEMetrics.   

1/14/2014 9:47:44 AM - Info dbclient(pid=3668) INF - OPERATION #3 of batch C:\Program Files\Veritas\NetBackup\DbExt\MsSql\F.bch FAILED with STATUS 1 (0 is normal). Elapsed time = 2(2) seconds.

1/14/2014 9:47:46 AM - Info dbclient(pid=3668) INF - Results of executing <C:\Program Files\Veritas\NetBackup\DbExt\MsSql\F.bch>:      

1/14/2014 9:47:46 AM - Info dbclient(pid=3668) <0> operations succeeded. <3> operations failed.       

1/14/2014 9:47:47 AM - Info dbclient(pid=3668) INF - The following object(s) were not backed up successfully.   

1/14/2014 9:47:47 AM - Info dbclient(pid=3668) INF - LcsCDR          

1/14/2014 9:47:47 AM - Info dbclient(pid=3668) INF - mgc          

1/14/2014 9:47:47 AM - Info dbclient(pid=3668) INF - QoEMetrics          

1/14/2014 9:48:07 AM - Error bpbrm(pid=10120) from client sipc-lyncdb: ERR - command failed: none of the requested files were backed up (2)

1/14/2014 9:48:07 AM - Error bpbrm(pid=10120) from client sipc-lyncdb: ERR - bphdb exit status = 2: none of the requested files were backed up

1/14/2014 9:48:09 AM - Info bphdb(pid=4172) done. status: 2: none of the requested files were backed up  

1/14/2014 9:48:09 AM - end writing

none of the requested files were backed up(2)

[RiaanBadenhorst]

Hi,

You have a permission error. You're running the netbackup client services as a local system account which translates to NT AUTHORITY\SYSTEM when trying to access the database. It fails as it has no rights on the database lcsCDR.

Either give the account mentioned above right, or start the clients service with a domain account with rights.

1/14/2014 9:47:35 AM - Info dbclient(pid=3668) DBMS MSG - ODBC return code <-1>, SQL State <08004>, SQL Message <916><[Microsoft][ODBC SQL Server Driver][SQL Server]The server principal "NT AUTHORITY\SYSTEM" is not able to access the database "LcsCDR" under the current security context.>.

[Marianne · Accepted solution]

Change NetBackup Client Service to use same logon account the user that you use for login to the server when you manually run .bch script.

[BasigDegrasia3]

Great

Thanks alot Marianne

it is running fine now when i changed the user used for Netbackup Client Service.

[Marianne]

Thanks for the feedback and solution, but Riaan was first to say:

... or start the clients service with a domain account with rights. 

You may want to clear the Solution and mark Riaan's post...

Thanks!

[BasigDegrasia3]

Oh

thanks all of yiou guys,

i am sorry Riaan, i was looking for the last post.