Quantcast
Channel: Symantec Connect - Backup and Recovery - Discussions
Viewing all articles
Browse latest Browse all 2300

media write error (84) in VMWare Backup.

$
0
0
I need a solution

Hi 

have observed that my VMware Backups are getting failed with error media write error (84), we are using netbackup 7.6.1.1 on windows 2008 R2 Enterprise 64 bit Platform.

please find the job details below

6/6/2015 9:07:39 AM - Info nbjm(pid=22060) starting backup job (jobid=611356) for client PBAD-DC2, policy VMWare_Daily_SAN_Backup, schedule Daily  
6/6/2015 9:07:40 AM - estimated 31632424 Kbytes needed
6/6/2015 9:07:40 AM - Info nbjm(pid=22060) started backup (backupid=PBAD-DC2_1433570859) job for client PBAD-DC2, policy VMWare_Daily_SAN_Backup, schedule Daily on storage unit Netbackup_StorageUnit using backup host pbad-netbackup.pbad.sbg.com.sa
6/6/2015 9:07:40 AM - started process bpbrm (4832)
6/6/2015 9:07:41 AM - Info bpbrm(pid=4832) PBAD-DC2 is the host to backup data from     
6/6/2015 9:07:41 AM - Info bpbrm(pid=4832) reading file list for client        
6/6/2015 9:07:42 AM - Info bpbrm(pid=4832) accelerator enabled           
6/6/2015 9:07:45 AM - Info bpbrm(pid=4832) starting bpbkar32 on client         
6/6/2015 9:07:45 AM - connecting
6/6/2015 9:07:45 AM - connected; connect time: 0:00:00
6/6/2015 9:07:46 AM - Info bpbkar32(pid=21892) Backup started           
6/6/2015 9:07:47 AM - Info bpbkar32(pid=21892) accelerator enabled backup, archive bit processing:<disabled>       
6/6/2015 9:07:47 AM - Info bptm(pid=1148) start            
6/6/2015 9:07:47 AM - Info bptm(pid=1148) using 524288 data buffer size        
6/6/2015 9:07:47 AM - Info bptm(pid=1148) setting receive network buffer to 2098176 bytes      
6/6/2015 9:07:47 AM - Info bptm(pid=1148) using 128 data buffers         
6/6/2015 9:07:48 AM - Info bptm(pid=1148) start backup           
6/6/2015 9:07:50 AM - begin writing
6/6/2015 9:09:18 AM - Info bpbkar32(pid=21892) INF - Transport Type =  nbd      
6/6/2015 9:09:34 AM - Critical bptm(pid=1148) A portion of data to be included from a previous backup (backupid = PBAD-DC2_1432943456, offset = 350832640, length = 131072) has incorrect checksum (calculated checksum from backup image 5a7a8e94f27c3c162e8c867b44df2cda1c09868b, expected checksum aa80546d788b65a523243bd49e5544e1d4163e9e)
6/6/2015 9:09:34 AM - Critical bptm(pid=1148) image write failed: error -1: plugin error      
6/6/2015 9:09:47 AM - Error bptm(pid=1148) cannot write image to disk, Invalid argument      
6/6/2015 9:09:47 AM - Info bptm(pid=1148) EXITING with status 84 <----------        
6/6/2015 9:09:47 AM - Error bpbrm(pid=4832) from client PBAD-DC2: ERR - tar file write error (14)   
6/6/2015 9:09:48 AM - Info bpbkar32(pid=21892) accelerator sent 0 bytes out of 0 bytes to server, optimization 0.0% 
6/6/2015 9:09:49 AM - Info bpbkar32(pid=21892) bpbkar waited 11 times for empty buffer, delayed 651 times.   
6/6/2015 9:09:50 AM - Info pbad-netbackup.pbad.sbg.com.sa(pid=1148) StorageServer=PureDisk:pbad-netbackup.pbad.sbg.com.sa; Report=PDDO Stats for (pbad-netbackup.pbad.sbg.com.sa): scanned: 342792 KB, CR sent: 13062 KB, CR sent over FC: 0 KB, dedup: 96.2%, cache disabled
6/6/2015 9:09:50 AM - Error bpbrm(pid=4832) could not send server status message       
6/6/2015 9:09:51 AM - Critical bpbrm(pid=4832) unexpected termination of client PBAD-DC2        
6/6/2015 9:10:01 AM - Info bpbkar32(pid=0) done. status: 84: media write error       
6/6/2015 9:10:01 AM - end writing; write time: 0:02:11
media write error (84)


Viewing all articles
Browse latest Browse all 2300

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>