Calling Netbackup from SQL Job

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2008 » SQL Server 2008 - General » Calling Netbackup from SQL Job

Calling Netbackup from SQL Job

Rate Topic

Display Mode

Topic Options

Author

Message

matt.gyton

Posted Friday, October 05, 2012 9:29 AM

SSC Rookie

Group: General Forum Members
Last Login: Thursday, April 25, 2013 8:45 AM
Points: 43, Visits: 142

Hi there,

I am trying to initiate a Netbackup task from a SQL Job using the following CmdExec code:

"C:\Program Files\VERITAS\NetBackup\bin\dbbackex.exe" -f "C:\Program Files\Veritas\NetBackup\DbExt\MsSql\<Filename.bch>" -p <profilename> -u <username> -pw <password> -s <server> -np

If I run it from a Command Prompt window it works fine, however if I copy the exact same code into a SQL Job and use the job type 'Operating System (CmdExec)' it fails to run. All I get in the Job History is:

"Executed as user: Domain\Username. The step did not generate any output. Process Exit Code 2. The step failed."

I have managed to get this to work on another almost identical server using the same accounts and everything but for some reason it won't run on the one I'm currently using.

Any suggestions? Anything that needs to be enabled on the server perhaps?

Thanks,

Matt

Post #1369146

TheGreenShepherd

Posted Friday, October 05, 2012 9:33 AM

Mr or Mrs. 500

Group: General Forum Members
Last Login: Thursday, May 02, 2013 3:40 PM
Points: 522, Visits: 374

If you right click on SQL Server Agent in SSMS and then go to Properties -> Job System, is the box checked to use a non-admin proxy account?

Post #1369150

matt.gyton

Posted Monday, October 08, 2012 2:45 AM

SSC Rookie

Group: General Forum Members
Last Login: Thursday, April 25, 2013 8:45 AM
Points: 43, Visits: 142

No, it's actually greyed out (presumably because we don't have any)....although on the server it is working on it's also the same.

Post #1369672

matt.gyton

Posted Monday, October 08, 2012 9:52 AM

SSC Rookie

Group: General Forum Members
Last Login: Thursday, April 25, 2013 8:45 AM
Points: 43, Visits: 142

Just in case anyone is interested I managed to resolve this issue....

I simply added the account running SQL Agent to the local admin group on the server, then restarted the SQL Agent service Smile

Post #1369912

« Prev Topic | Next Topic »

Permissions