Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

media write error (84)

Created: 31 Oct 2009 • Updated: 10 Feb 2013 | 3 comments
YazZ's picture
This issue has been solved. See solution.

Hi every body, hope you are all fine,

I am now implementing Net backup 6.5 Enterprise Server installation on Red Hat server (enterprise 5.2), to perform a file backup to another servers, which is also Red Hat, using remote agents.Our environment consists of one master server,2 standard agents installed on 2 servers, one IBM tape library (has 2 tape drives), one SAN, data we want to backup are on SAN.

Backing up data completed successfully from 2 servers to disk (either to SAN or attached to master server), but when trying to perform backup to tape it is failed.

here job log :

10/28/2009 01:34:49 - requesting resource backup-srv.NBU_CLIENT.MAXJOBS.db-1
10/28/2009 01:34:49 - requesting resource backup-srv-hcart3-robot-tld-0
10/28/2009 01:34:49 - requesting resource backup-srv.NBU_CLIENT.MAXJOBS.db-1
10/28/2009 01:34:49 - requesting resource backup-srv.NBU_POLICY.MAXJOBS.test-DB1
10/28/2009 01:34:49 - granted resource  backup-srv.NBU_CLIENT.MAXJOBS.db-1
10/28/2009 01:34:49 - granted resource  backup-srv.NBU_POLICY.MAXJOBS.test-DB1
10/28/2009 01:34:49 - granted resource  021AL3
10/28/2009 01:34:49 - granted resource  IBM.ULT3580-TD3.000
10/28/2009 01:34:49 - granted resource  backup-srv-hcart3-robot-tld-0
10/28/2009 01:34:49 - estimated 38 kbytes needed
10/28/2009 01:34:49 - begin Parent Job
10/28/2009 01:34:49 - begin Stream Discovery: Start Notify Script
10/28/2009 01:34:49 - started process RUNCMD (pid=13076)
Operation Status: 0
10/28/2009 01:34:50 - end Stream Discovery: Start Notify Script; elapsed time 0:00:01
10/28/2009 01:34:50 - begin Stream Discovery: Stream Discovery
Operation Status: 0
10/28/2009 01:34:50 - end Stream Discovery: Stream Discovery; elapsed time 0:00:00
10/28/2009 01:34:50 - begin Stream Discovery: Policy Execution Manager Preprocessed
Operation Status: 800
10/28/2009 02:03:55 - end Stream Discovery: Policy Execution Manager Preprocessed; elapsed time 0:29:05
10/28/2009 02:03:55 - begin Stream Discovery: Stop On Error
Operation Status: 0
10/28/2009 02:03:55 - end Stream Discovery: Stop On Error; elapsed time 0:00:00
10/28/2009 02:03:55 - begin Stream Discovery: End Notify Script
10/28/2009 02:03:55 - started process RUNCMD (pid=15204)
Operation Status: 0
10/28/2009 02:03:55 - end Stream Discovery: End Notify Script; elapsed time 0:00:00
Operation Status: 800
10/28/2009 02:03:55 - end Parent Job; elapsed time 0:29:06
resource request failed (800)

10/28/2009 01:34:50 - requesting resource backup-srv-hcart3-robot-tld-0
10/28/2009 01:34:50 - requesting resource backup-srv.NBU_CLIENT.MAXJOBS.db-1
10/28/2009 01:34:50 - requesting resource backup-srv.NBU_POLICY.MAXJOBS.test-DB1
10/28/2009 01:34:50 - awaiting resource backup-srv.NBU_CLIENT.MAXJOBS.db-1. Resource is busy, will retry allocation later.
10/28/2009 02:03:03 - awaiting resource backup-srv-hcart3-robot-tld-0. No drives are available.
10/28/2009 02:03:54 - Error nbjm (pid=8573) NBU status: 800, EMM status: All compatible drive paths are down, but media is available
resource request failed (800)

& other time like following:

10/28/2009 18:07:15 - estimated 0 kbytes needed
10/28/2009 18:07:16 - started process bpbrm (pid=7553)
10/28/2009 18:07:16 - connecting
10/28/2009 18:07:16 - connected; connect time: 0:00:00
10/28/2009 18:07:20 - mounting 020AL3
10/28/2009 18:07:33 - Error bptm (pid=7559) error requesting media, TpErrno = Robot operation failed
10/28/2009 18:07:33 - Warning bptm (pid=7559) media id 020AL3 load operation reported an error
10/28/2009 18:07:33 - current media 020AL3 complete, requesting next media Any
10/28/2009 18:07:51 - granted resource  020AL3
10/28/2009 18:07:51 - granted resource  IBM.ULT3580-TD3.000
10/28/2009 18:07:51 - granted resource  backup-srv-hcart3-robot-tld-0
10/28/2009 18:07:51 - mounting 020AL3
10/28/2009 18:08:56 - mounted 020AL3; mount time: 0:01:05
10/28/2009 18:08:56 - positioning 020AL3 to file 5
10/28/2009 18:09:09 - positioned 020AL3; position time: 0:00:13
10/28/2009 18:09:09 - begin writing
10/28/2009 18:48:25 - Error bptm (pid=7559) cannot write image to media id 020AL3, drive index 0, Input/output error
10/28/2009 18:48:25 - Error bpbrm (pid=7553) from client backup-srv: ERR - bpbkar exiting because backup is aborting
10/28/2009 18:48:25 - end writing; write time: 0:39:16
media write error (84)

 

 

 

Comments 3 CommentsJump to latest comment

Marianne's picture

You need to determine if you have device or media problems.
Can you use robtest to mount a blank tape and use tar to write a backup?

To troubleshoot from NetBackup perspective, create bptm log on media server. Also add VERBOSE entry to /usr/openv/volmgr/vm.conf  and restart NetBackup.
Device errors will now be logged to /var/log/messages.

Also have a look at the In-Depth troubleshooting guide for status 84:
exftpp.symantec.com/pub/support/products/NetBackup_Enterprise_Server/273908.pdf

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

SOLUTION
Pablo_B's picture

Some kind of I/O error
 To troubleshoot this error, you need to collect syslog messages and turn on bptm logs. You may have media, drive or connetion issues that are typical to 84 errors. These logs will help you isolate your particular issue. This error can also be generated when the latest driver for the tape drive is not installed.

A few more things you can check:

-Clean the drive.
-Try new media. Could be a defective tape. Freeze the tape so that it will not try to use it and let it grab another.
 -Verify that the drive is configured correctly Fixed mode vs. Variable mode.

More that are probably not your issue:
-Verify correct media type is being used for your drive. LTO3 in LTO3 compatible drive
   Designate the media correctly on the media server. (HCART2, HCART, etc...)
- Check that the fragment size configured for your disk storage unit is not larger than the max file size that the O.S. specifies. I.E, O.S, doesn't support files larger than 2gig.  (Not your problem with RHEL 5.2)

Zahid.Haseeb's picture

 See this it may help you

http://seer.entsupport.symantec.com/docs/275066.htm

http://seer.entsupport.symantec.com/docs/272802.htm

https://www-secure.symantec.com/connect/forums/consistent-media-write-error-84



Any comment will be appreciated. Mark as Solution if your query is resolved
__________________
Thanks in Advance
Zahid Haseeb

zahidhaseeb.wordpress.com