May 18, 2018 at 7:43 am
Hello all,
First of all let me clarify that I've entered the DBA world not too long ago and inherited a few systems/practices that I haven't used before. I'm having some issues setting up a job to do full and transaction log backups for databases on a sql server 2016 instance. The application used for the backups is Veritas Netbackup.
When running the job, I'm getting the following error:
Message
Executed as user: domain\user. The step did not generate any output. Process Exit Code 2. The step failed.
I have the CmdExec logging turned on in the advanced section of the job step, but it does not output anything to that file either. I checked the event viewer on the windows server and I'm not seeing anything either.
The step is running the following command as the SQL Server Agent Service Account:
"C:\Program Files\Veritas\NetBackup\bin\dbbackex" -f "G:\\Netbackup\TLogBackup.bch" -np
These are the batch file contents:
OPERATION BACKUP
DATABASE $ALL
EXCLUDE master
EXCLUDE msdb
OBJECTTYPE TRXLOG
SQLHOST host_info
NBSERVER netbackup_server_info
MAXTRANSFERSIZE 6
BLOCKSIZE 7
POLICY policy_name
ENDOPER TRUE
I am not sure what is causing this job to fail. Any ideas?
Thanks!
May 18, 2018 at 9:08 am
Does the statement work outside sql server agent? It might be a permission problem.
You can run sql agent jobs under a different windows account using proxies and credentials
May 18, 2018 at 9:35 am
Jo Pattyn - Friday, May 18, 2018 9:08 AMDoes the statement work outside sql server agent? It might be a permission problem.
You can run sql agent jobs under a different windows account using proxies and credentials
I just noticed I made a typo when adding the command to my OP. It should be "C:\Program Files\Veritas\NetBackup\bin\dbbackex.exe" -f "G:\\Netbackup\TLogBackup.bch" -np
Anyway, the statement works on the cmd prompt on the server itself. If I run the batch file from the server it will backup everything correctly. I granted admin rights to the server for the sql agent service account as well as the backup service account. I'm still not seeing any errors on my side and the NBU admin says there are no errors on his side either.
I'm going to create a proxy for this backup and run it with that instead to see if it works. Thanks!
May 18, 2018 at 10:06 am
You may want to check the following article to see if it helps - it's similar to your issues:
STATUS CODE 2: Microsoft SQL backups fail with a NetBackup Status Code 2 "none of the requested files were backed up"
And this has some additional troubleshooting suggestions:
How to troubleshoot Microsoft SQL Server database backup issues
Sue
May 18, 2018 at 12:44 pm
Sue_H - Friday, May 18, 2018 10:06 AMYou may want to check the following article to see if it helps - it's similar to your issues:
STATUS CODE 2: Microsoft SQL backups fail with a NetBackup Status Code 2 "none of the requested files were backed up"
And this has some additional troubleshooting suggestions:
How to troubleshoot Microsoft SQL Server database backup issuesSue
Thank you. I followed all steps and recommendations by the articles but I'm still unable to get the backup job to work.
I'll be honest, I gave up and moved away from this legacy backup and set my jobs up to use bpbackup instead. It looks like everything is working correctly with this setting instead.
May 18, 2018 at 12:51 pm
druid84 - Friday, May 18, 2018 12:44 PMSue_H - Friday, May 18, 2018 10:06 AMYou may want to check the following article to see if it helps - it's similar to your issues:
STATUS CODE 2: Microsoft SQL backups fail with a NetBackup Status Code 2 "none of the requested files were backed up"
And this has some additional troubleshooting suggestions:
How to troubleshoot Microsoft SQL Server database backup issuesSue
Thank you. I followed all steps and recommendations by the articles but I'm still unable to get the backup job to work.
I'll be honest, I gave up and moved away from this legacy backup and set my jobs up to use bpbackup instead. It looks like everything is working correctly with this setting instead.
Just curious...did you get anything at all in the log file?
Sue
May 18, 2018 at 1:04 pm
Sue_H - Friday, May 18, 2018 12:51 PMdruid84 - Friday, May 18, 2018 12:44 PMSue_H - Friday, May 18, 2018 10:06 AMYou may want to check the following article to see if it helps - it's similar to your issues:
STATUS CODE 2: Microsoft SQL backups fail with a NetBackup Status Code 2 "none of the requested files were backed up"
And this has some additional troubleshooting suggestions:
How to troubleshoot Microsoft SQL Server database backup issuesSue
Thank you. I followed all steps and recommendations by the articles but I'm still unable to get the backup job to work.
I'll be honest, I gave up and moved away from this legacy backup and set my jobs up to use bpbackup instead. It looks like everything is working correctly with this setting instead.
Just curious...did you get anything at all in the log file?
Sue
the dbclient log within Netbackup did start adding logs after I made a few changes. It did help me troubleshoot, but I ended up making too many changes and granting the service account too many rights to the sql instance. Even after these changes, the job kept failing. Our NBU admin couldn't figure this out either but he may contact Veritas directly for assistance.
As a workaround I have SQL Server Agent run some stored procedures for integrity checks, creating the backups, and then sending the files to the netbackup server through bpbackup. It seems to work smoothly.
May 18, 2018 at 1:32 pm
druid84 - Friday, May 18, 2018 1:04 PMthe dbclient log within Netbackup did start adding logs after I made a few changes. It did help me troubleshoot, but I ended up making too many changes and granting the service account too many rights to the sql instance. Even after these changes, the job kept failing. Our NBU admin couldn't figure this out either but he may contact Veritas directly for assistance.
As a workaround I have SQL Server Agent run some stored procedures for integrity checks, creating the backups, and then sending the files to the netbackup server through bpbackup. It seems to work smoothly.
Those agents, client pieces for some of the backup software can be a pain sometimes. It usually is permissions but the vendors often don't document it very well. Or they assume anywhere those run, they will be an administrator of anything and everything. Good that you caught yours and went a different direction for now.
Sue
May 30, 2018 at 1:59 pm
Sue_H - Friday, May 18, 2018 1:32 PMdruid84 - Friday, May 18, 2018 1:04 PMthe dbclient log within Netbackup did start adding logs after I made a few changes. It did help me troubleshoot, but I ended up making too many changes and granting the service account too many rights to the sql instance. Even after these changes, the job kept failing. Our NBU admin couldn't figure this out either but he may contact Veritas directly for assistance.
As a workaround I have SQL Server Agent run some stored procedures for integrity checks, creating the backups, and then sending the files to the netbackup server through bpbackup. It seems to work smoothly.Those agents, client pieces for some of the backup software can be a pain sometimes. It usually is permissions but the vendors often don't document it very well. Or they assume anywhere those run, they will be an administrator of anything and everything. Good that you caught yours and went a different direction for now.
Sue
I was finally able to get back to this in a testing environment and found the issues. For dbbackex to work correctly you need to update the Netbackup Legacy Network Service, Netbackup Legacy Client Service, and Netbackup Client Service Window Services to include the information of the same service account being used by the Netbackup client. Also, this service account needs to be admin of the server and sysadmin of the SQL instance.
May 31, 2018 at 2:07 am
Glad you found it.
Thanks for the solution
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply