Video Screencast Help

got ERROR 85 when try Restore.

Created: 27 Feb 2014 • Updated: 16 May 2014 | 8 comments
This issue has been solved. See solution.
Hi All,
 
Below are the contents of detailed status restore job.
 
Netbackup version is 7.5.0.5
 
Please help in sorting.. thank you.
 
26/02/2014 11:45:16 - Info bpbrm (pid=5238) brmogsdb01 is the host to restore to
26/02/2014 11:45:17 - Info bpbrm (pid=5238) telling media manager to start restore on client
26/02/2014 11:45:17 - Info bpbrm (pid=5238) spawning a brm child process
26/02/2014 11:45:17 - Info bpbrm (pid=5238) child pid: 5242
26/02/2014 11:45:17 - connecting
26/02/2014 11:45:18 - Info bpbrm (pid=5242) start tar on client
26/02/2014 11:45:18 - Info tar (pid=9080) Restore started.
26/02/2014 11:45:18 - connected; connect time: 0:00:00
26/02/2014 11:45:19 - Info bptm (pid=5240) Waiting for mount of media id 0013L5 (copy 1) on server brmogmed01.
26/02/2014 11:45:19 - started process bptm (pid=5240)
26/02/2014 11:45:19 - mounting 0013L5
26/02/2014 11:45:20 - Info bptm (pid=5240) INF - Waiting for mount of media id 0013L5 on server brmogmed01 for reading.
26/02/2014 11:46:23 - mounted 0013L5; mount time: 0:01:04
26/02/2014 11:46:23 - Info bptm (pid=5240) 0013L5
26/02/2014 11:46:24 - Info bptm (pid=5240) INF - Waiting for positioning of media id 0013L5 on server brmogmed01 for reading.
26/02/2014 11:46:24 - positioning 0013L5 to file 109
26/02/2014 11:47:26 - positioned 0013L5; position time: 0:01:02
26/02/2014 11:47:26 - begin reading
26/02/2014 11:47:27 - Error bptm (pid=5240) cannot read image from media id 0013L5, drive index 1, Device or resource busy
26/02/2014 11:47:28 - Error bptm (pid=5241) The following files/folders were not restored:
26/02/2014 11:47:28 - Error bptm (pid=5241) UTF - /db/oradata/oracdw/
26/02/2014 11:47:28 - Error bptm (pid=5241) UTF - /db/oradata/oracdw/DATSPACE0203.dbf
26/02/2014 11:47:28 - Error bptm (pid=5241) UTF - /db/oradata/oracdw/repeul02.dbf
26/02/2014 11:47:28 - Error bptm (pid=5241) UTF - /db/oradata/oracdw/DATSPACE0104.dbf
26/02/2014 11:47:28 - Error bptm (pid=5241) UTF - /db/oradata/oracdw/sysaux01.dbf
26/02/2014 11:47:28 - Error bptm (pid=5241) UTF - /db/oradata/oracdw/temp01.dbf
26/02/2014 11:47:28 - Error bptm (pid=5241) UTF - /db/oradata/oracdw/sqlnet.log
26/02/2014 11:47:28 - Error bptm (pid=5241) UTF - /db/oradata/oracdw/DATASPACE0102.dbf
26/02/2014 11:47:29 - Error bptm (pid=5241) UTF - /db/oradata/oracdw/DATASPACE05.dbf
26/02/2014 11:47:29 - Error bptm (pid=5241) UTF - /db/oradata/oracdw/INDSPACE0103.dbf
26/02/2014 11:47:29 - Error bptm (pid=5241) more than 10 files were not restored, remaining ones are shown in the progress log.
26/02/2014 11:47:29 - Info bpbrm (pid=5238) got ERROR 85 from media manager
26/02/2014 11:47:29 - Info bpbrm (pid=5238) terminating bpbrm child 5242 jobid=153346
26/02/2014 14:55:30 - begin Restore
26/02/2014 14:55:31 - number of images required: 1
26/02/2014 14:55:31 - media needed: 0013L5
26/02/2014 14:55:31 - media needed: 0034L5
26/02/2014 14:56:03 - restoring from image brspdb01_1393211400
26/02/2014 14:56:07 - requesting resource 0013L5
26/02/2014 14:56:07 - granted resource  0013L5
26/02/2014 14:56:07 - granted resource  HP.ULTRIUM5-SCSI.004
26/02/2014 14:58:17 - restored from image brspdb01_1393211400; restore time: 0:02:14
26/02/2014 14:58:17 - Warning bprd (pid=14874) Restore must be resumed prior to first image expiration on Seg 03 Mar 2014 00:10:00 BRT
26/02/2014 14:58:17 - end Restore; elapsed time 0:02:47
Failed to get status code information (2850)
 
Operating Systems:
Discussion Filed Under:

Comments 8 CommentsJump to latest comment

Nicolai's picture

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.log).

Assumption is the mother of all mess ups.

If this post answered your'e qustion -  Please mark as a soloution.

Marianne's picture

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:

SPC-2 SCSI reserve in HP-UX:
   Set the st_ats_enabled kernel parameter to 0 (zero) .
 
HP-UX EMS Tape Device Monitor:
■ To disable EMS completely, run the HP-UX Hardware Monitoring Request
Manager and select (K) kill (disable) Monitoring.
Invoke the Hardware Monitoring Request Manager by using the
/etc/opt/resmon/lbin/monconfig command.
■ To configure EMS so it does not log any events or poll devices, set the
POLL_INTERVAL value to 0 (zero). The POLL_INTERVAL parameter is in the
following HP-UX configuration file:
/var/stm/config/tools/monitor/dm_stape.cfg

(Information taken from NBU Device Config Guide)

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Nicolai's picture

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. 

Assumption is the mother of all mess ups.

If this post answered your'e qustion -  Please mark as a soloution.

Mark_Solutions's picture

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

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

Michael G Andersen's picture

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

SOLUTION
fernando.santos's picture

Michael Thanks for help.

your tip was the way to solution

Michael G Andersen's picture

Glad I could help you recover your data