10-14-2010 11:37 AM
Maybe one of these days I can get back into answering as well as asking questions, but for now, its going to have to be asking.
So we were able to get the linking worked out - the linking script worked wonderfully btw.
So now the backup is failing of course with an exit status 6. When looking at the bphdb logs, we see that NetBackup can't find the script:
11:01:10.393 [561180] <32> bphdb do_backup: FTL - Child exec of <path_to_script> failed.
11:01:10.393 [561180] <32> bphdb do_backup: errno = 2: No such file or directory
11:01:10.393 [561180] <16> bphdb Exit: ERR - bphdb exit status = 29: failed trying to exec a command
The SAP specific logs are empty b/c it appears that NetBackup isn't even getting to SAP at this point. We have verified that all directories in the chain have proper ownershit, and have permissions set to 775.
Any suggestions?
Solved! Go to Solution.
10-14-2010 11:55 AM
Can we maybe 1st get clarification - are you using backint (SAP) or rman (Oracle) backup method?
The oracle_link script assumes that you are using the rman method, right?
Next question - did you use any of the sample scripts? e.g. sap_rman_backup (Oracle with RMAN)?
Did you carefully check the path specified in policy backup selection with the actual path on the client?
Does the backup script contain "su - user " to ensure script is executed with proper permissions?
Have you tried to run the script from cmd on the client?
http://www.symantec.com/business/support/index?page=content&id=TECH52817
10-14-2010 11:55 AM
Can we maybe 1st get clarification - are you using backint (SAP) or rman (Oracle) backup method?
The oracle_link script assumes that you are using the rman method, right?
Next question - did you use any of the sample scripts? e.g. sap_rman_backup (Oracle with RMAN)?
Did you carefully check the path specified in policy backup selection with the actual path on the client?
Does the backup script contain "su - user " to ensure script is executed with proper permissions?
Have you tried to run the script from cmd on the client?
http://www.symantec.com/business/support/index?page=content&id=TECH52817
10-15-2010 01:10 AM
I agree with Marianne - run script by hand. Even warning from e.g. the time command may result in RC 29. But in you're example I think it's a missing directory "errno = 2: No such file or directory". Have you created /usr/openv/netbackup/logs/user_ops with dba writing rights or the or alike for Windows ?.