Forum Discussion

Kushaal's avatar
Kushaal
Level 4
11 years ago

Backup failingwith status code 84

Hi,Backup is failing with below error

12/16/2013 11:45:59 AM - Info nbjm(pid=5312) starting backup job (jobid=1010676) for client 10.6.41.73, policy ch9985vmig1, schedule Full  
12/16/2013 11:45:59 AM - Info nbjm(pid=5312) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=1010676, request id:{5FDBA605-900F-4498-BF4A-2A76C0BF932E})  
12/16/2013 11:45:59 AM - requesting resource chcitmsbkp02-hcart2-robot-tld-6
12/16/2013 11:45:59 AM - requesting resource citbknbu02.NBU_CLIENT.MAXJOBS.10.6.41.73
12/16/2013 11:45:59 AM - requesting resource citbknbu02.NBU_POLICY.MAXJOBS.ch9985vmig1
12/16/2013 11:46:00 AM - granted resource citbknbu02.NBU_CLIENT.MAXJOBS.10.6.41.73
12/16/2013 11:46:00 AM - granted resource citbknbu02.NBU_POLICY.MAXJOBS.ch9985vmig1
12/16/2013 11:46:00 AM - granted resource DW1102
12/16/2013 11:46:00 AM - granted resource Drive019
12/16/2013 11:46:00 AM - granted resource chcitmsbkp02-hcart2-robot-tld-6
12/16/2013 11:46:00 AM - estimated 0 Kbytes needed
12/16/2013 11:46:00 AM - Info nbjm(pid=5312) started backup (backupid=10.6.41.73_1387174560) job for client 10.6.41.73, policy ch9985vmig1, schedule Full on storage unit chcitmsbkp02-hcart2-robot-tld-6
12/16/2013 11:46:02 AM - started process bpbrm (5320)
12/16/2013 11:46:09 AM - Info bpbrm(pid=5320) 10.6.41.73 is the host to backup data from     
12/16/2013 11:46:09 AM - Info bpbrm(pid=5320) reading file list from client        
12/16/2013 11:46:09 AM - connecting
12/16/2013 11:46:13 AM - Info bpbrm(pid=5320) starting bpbkar32 on client         
12/16/2013 11:46:13 AM - connected; connect time: 00:00:04
12/16/2013 11:46:14 AM - Info bpbkar32(pid=2388) Backup started           
12/16/2013 11:46:14 AM - Info bptm(pid=5796) start            
12/16/2013 11:46:15 AM - Info bptm(pid=5796) using 65536 data buffer size        
12/16/2013 11:46:15 AM - Info bptm(pid=5796) setting receive network buffer to 263168 bytes      
12/16/2013 11:46:15 AM - Info bptm(pid=5796) using 30 data buffers         
12/16/2013 11:46:15 AM - Info bptm(pid=5796) start backup           
12/16/2013 11:46:15 AM - Info bptm(pid=5796) backup child process is pid 5392.1276       
12/16/2013 11:46:15 AM - Info bptm(pid=5796) Waiting for mount of media id DW1102 (copy 1) on server chcitmsbkp02.lntcorp.lntuniverse.com. 
12/16/2013 11:46:16 AM - Info bptm(pid=5392) start            
12/16/2013 11:46:16 AM - mounting DW1102
12/16/2013 11:47:24 AM - Info bptm(pid=5796) media id DW1102 mounted on drive index 4, drivepath {2,0,0,0}, drivename Drive019, copy 1
12/16/2013 11:47:24 AM - mounted; mount time: 00:01:08
12/16/2013 11:47:32 AM - positioning DW1102 to file 1
12/16/2013 11:47:47 AM - positioned DW1102; position time: 00:00:15
12/16/2013 11:47:47 AM - begin writing
12/16/2013 2:07:01 PM - Info bpbkar32(pid=2388) change journal NOT enabled for <G:\>       
12/17/2013 12:16:03 AM - current media DW1102 complete, requesting next resource Any
12/17/2013 12:16:03 AM - granted resource DW1106
12/17/2013 12:16:03 AM - granted resource Drive015
12/17/2013 12:16:03 AM - granted resource chcitmsbkp02-hcart2-robot-tld-6
12/17/2013 12:16:04 AM - Info bptm(pid=5796) Waiting for mount of media id DW1106 (copy 1) on server chcitmsbkp02.lntcorp.lntuniverse.com. 
12/17/2013 12:16:04 AM - end writing; write time: 12:28:17
12/17/2013 12:16:04 AM - mounting DW1106
12/17/2013 12:17:00 AM - Info bptm(pid=5796) media id DW1106 mounted on drive index 0, drivepath {1,0,0,0}, drivename Drive015, copy 1
12/17/2013 12:17:01 AM - mounted; mount time: 00:00:57
12/17/2013 12:17:09 AM - positioning DW1106 to file 1
12/17/2013 12:17:16 AM - Info bptm(pid=5796) WriteFile() failed err = 19        
12/17/2013 12:17:16 AM - Error bptm(pid=5796) write error on media id DW1106, drive index 0, writing header block, 19
12/17/2013 12:17:16 AM - Info bptm(pid=5796) EXITING with status 84 <----------        
12/17/2013 12:17:19 AM - Error bpbrm(pid=5320) cannot send mail to lntbackupadmin@lntinfotech.com,Vikas.Nalawade@lntinfotech.com        
12/17/2013 12:17:21 AM - Info bpbkar32(pid=2388) done. status: 84: media write error       
12/17/2013 12:17:21 AM - end writing
media write error(84)
 
kindly suggest.on how to resolve the issue
  • Is the media write protected ?

    STATUS CODE: 84 "Media Write Failed" error occurs consistently on certain media that are not known to be defective.

    http://www.symantec.com/docs/TECH39004

    Troubleshooting:

    Please look for messages similar to the following. Observe the "19" at the end of the line, following the write error on the media header. This is a message number reported by the OS, that can be translated with the net command. Typing net helpmsg 19 from a command prompt reports "The media is write protected." When this message is seen, write protection is the cause.

2 Replies

  • Similar issue over here: https://www-secure.symantec.com/connect/forums/vault-backup-0

    Media is probably bad. 
    Please eject that tape from the robot so that backup can be retried with another tape.

    Please enable logging before you retry the backup.
    On media server, create bptm folder under ...\netbackup\logs
    Add VERBOSE entry to ...\volmgr\vm.conf and restart NBU Device Management service.

    If errors are seen on other media and/or tape drive as well, check bptm log for errors (or post as File attachment) and check Event Viewer System and Application logs for device errors. 

  • Is the media write protected ?

    STATUS CODE: 84 "Media Write Failed" error occurs consistently on certain media that are not known to be defective.

    http://www.symantec.com/docs/TECH39004

    Troubleshooting:

    Please look for messages similar to the following. Observe the "19" at the end of the line, following the write error on the media header. This is a message number reported by the OS, that can be translated with the net command. Typing net helpmsg 19 from a command prompt reports "The media is write protected." When this message is seen, write protection is the cause.