Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Calling Netbackup from SQL Job Expand / Collapse
Author
Message
Posted Friday, October 5, 2012 9:29 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Thursday, July 17, 2014 3:18 AM
Points: 72, Visits: 226
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
Posted Friday, October 5, 2012 9:33 AM


Mr or Mrs. 500

Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500

Group: General Forum Members
Last Login: Tuesday, July 8, 2014 6:34 PM
Points: 565, Visits: 458
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
Posted Monday, October 8, 2012 2:45 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Thursday, July 17, 2014 3:18 AM
Points: 72, Visits: 226
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
Posted Monday, October 8, 2012 9:52 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Thursday, July 17, 2014 3:18 AM
Points: 72, Visits: 226
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
Post #1369912
Posted Monday, October 7, 2013 3:45 PM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Wednesday, April 2, 2014 10:19 AM
Points: 86, Visits: 539
Rather than giving the agent account administrative rights to the entire server, it might help if you read this.

http://fixunix.com/veritas-net-backup/481537-start-netbackup-sqlserveragent.html


SQL Agent needs rights to create temporary ODBC connections. So you modify the registry permssions and give the Agent Account full access to the Veritas folder.

Post #1502396
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse