02-27-2014 05:19 AM
Solved! Go to Solution.
05-08-2014 12:50 AM
The timeout issue might be solved by CLIENT_CONNECT_TIMEOUT and CLIENT_READ_TIMEOUT.
These values defaults to 60 seconds and 300 seconds, which is not always sufficient for database restores.
Regards
Michael
02-27-2014 05:30 AM
see if the below T/Ns are valid in your case
http://www.symantec.com/business/support/index?page=content&id=TECH65340
http://www.symantec.com/business/support/index?page=content&id=TECH169487
02-27-2014 05:35 AM
Netbackup status code 85:
http://www.symantec.com/docs/HOWTO34969
Inspect messages/syslog as well for error messages (HP-UX logs such messages in in /var/opt/resmon/log/event.
02-27-2014 06:12 AM
26/02/2014 11:47:27 - Error bptm (pid=5240) cannot read image from media id 0013L5, drive index 1, Device or resource busy
Please tell us more about this environment... Was backup done by a media server with Media Server Encryption Option?
If not, we are going to need logs.
On media server, level 5 bptm log.
Also add VERBOSE entry to /usr/openv/volmgr/vm.conf and restart NBU.
NBU will now log Media Manager actions/errors to syslog (/var/adm/syslog/syslog.log).
Please also check that the following has been disabled on HP-UX media server:
(Information taken from NBU Device Config Guide)
02-27-2014 07:04 AM
Disabling HP ESM is no longer needed.
I had the same issues at HP-UX 11.11 (or was it 11.00) and was fixed with a patch.
Fernando : Unless you are running a really old unpatched version of HP-UX it should not be necessary.
02-27-2014 10:34 AM
This looks like an oracle restore?
Where are you running it from?
If doing rman backups then it should be done from rman and not the BAR (Though OpsCenter gives new possibilities too)
Give us more details so that we can help
#EDIT#
Having re-read your initial post .iIt looks like you may have 2 errors here - one that resources are busy and the second part of the restore hitting a timeout
What are your media mount and client read timeouts set to? -you get the second failure after a few minutes
05-08-2014 12:50 AM
The timeout issue might be solved by CLIENT_CONNECT_TIMEOUT and CLIENT_READ_TIMEOUT.
These values defaults to 60 seconds and 300 seconds, which is not always sufficient for database restores.
Regards
Michael
05-16-2014 07:27 AM
Michael Thanks for help.
your tip was the way to solution
05-17-2014 02:37 AM
Glad I could help you recover your data