Video Screencast Help
Give us your opinion and win with Symantec! Please help us by taking this survey to tell us about your experience with Symantec Connect, so that we can continue to grow and improve.  Take the survey.

Full VMDK vs. "mapped" full vmdk backup issues with Linux VM

Created: 19 Mar 2013 • Updated: 19 Mar 2013

Netbackup 7.5.0.4, Windows 2008r2

Hello again.

I am having an odd issue with a couple linux VM's that will backup cleanly if I run them as a full VMDK backup, but when using a "mapped" full backup, the backup dies with the info below.

/19/2013 11:17:21 AM - Info nbjm(pid=4532) starting backup job (jobid=1644420) for client SSYN010L, policy Test_Pdc00gisa303l, schedule Weekly_Full 
3/19/2013 11:17:21 AM - Info nbjm(pid=4532) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=1644420, request id:{D42CBAE7-E6A4-4D49-96DD-1922193A628A}) 
3/19/2013 11:17:21 AM - requesting resource PDCDD_SU_1
3/19/2013 11:17:21 AM - requesting resource pdc00nbua801w.ohlogistics.com.NBU_CLIENT.MAXJOBS.SSYN010L
3/19/2013 11:17:21 AM - requesting resource pdc00nbua801w.ohlogistics.com.NBU_POLICY.MAXJOBS.Test_Pdc00gisa303l
3/19/2013 11:17:21 AM - granted resource pdc00nbua801w.ohlogistics.com.NBU_CLIENT.MAXJOBS.SSYN010L
3/19/2013 11:17:21 AM - granted resource pdc00nbua801w.ohlogistics.com.NBU_POLICY.MAXJOBS.Test_Pdc00gisa303l
3/19/2013 11:17:21 AM - granted resource MediaID=@aaaad;DiskVolume=PDCDisk1;DiskPool=PDCDD_DP;Path=PDCDisk1;StorageServer=pdc00ddma901;MediaServer=pdc00nbua802w
3/19/2013 11:17:21 AM - granted resource PDCDD_SU_1
3/19/2013 11:17:21 AM - estimated 0 Kbytes needed
3/19/2013 11:17:21 AM - Info nbjm(pid=4532) started backup (backupid=SSYN010L_1363709841) job for client SSYN010L, policy Test_Pdc00gisa303l, schedule Weekly_Full on storage unit PDCDD_SU_1
3/19/2013 11:17:23 AM - started process bpbrm (3252)
3/19/2013 11:17:25 AM - connecting
3/19/2013 11:17:25 AM - connected; connect time: 00:00:00
3/19/2013 11:17:37 AM - Info bpbkar32(pid=6780) Backup started          
3/19/2013 11:17:37 AM - Info bptm(pid=5768) start           
3/19/2013 11:17:37 AM - Info bptm(pid=5768) using 1048576 data buffer size       
3/19/2013 11:17:37 AM - Info bptm(pid=5768) setting receive network buffer to 1048576 bytes     
3/19/2013 11:17:37 AM - Info bptm(pid=5768) using 128 data buffers        
3/19/2013 11:17:41 AM - Info bptm(pid=5768) start backup          
3/19/2013 11:17:44 AM - begin writing
3/19/2013 11:18:03 AM - Error bpbrm(pid=3252) socket read failed, An existing connection was forcibly closed by the remote host.  (10054)
3/19/2013 11:18:13 AM - Error bpbrm(pid=3252) could not send server status message      
3/19/2013 11:18:14 AM - end writing; write time: 00:00:30
file read failed(13)

I have done a bit of research on the issue, and the closest things I found indicated that this was addressed in previous versions to what I am running. That appears not to be the case, unless something else is causing my issue. Apparently, being a Linux VM is significant to this particular problem. Any ideas? I'll provided what logs I can.  FYI, these VM's were perviously running well, and I am unaware of any changes made at the time this started.

Thank you,

Todd

Discussion Filed Under: