Video Screencast Help
Symantec Appoints Michael A. Brown CEO. Learn more.

system call failed(11) while backup VM through VMWARE policy Netbackup7.5

Created: 22 Aug 2012 | 3 comments

I'm trying to backup virtual machines but I'm getting error while backing up some virtual machines.

 

I'm using NB 7.5.3 and disk storage MSDP pool

 

21/08/2012 4:32:33 PM - Info nbjm(pid=6132) starting backup job (jobid=11474) for client MSH-SV-LDR-CWS, policy VoicenData, schedule Full 
21/08/2012 4:32:34 PM - estimated 0 Kbytes needed
21/08/2012 4:32:34 PM - Info nbjm(pid=6132) started backup (backupid=MSH-SV-LDR-CWS_1345581153) job for client MSH-SV-LDR-CWS, policy VoicenData, schedule Full on storage unit NBMEDS3
21/08/2012 4:32:35 PM - started process bpbrm (5056)
21/08/2012 4:32:42 PM - Info bpbrm(pid=5056) MSH-SV-LDR-CWS is the host to backup data from    
21/08/2012 4:32:42 PM - Info bpbrm(pid=5056) reading file list from client       
21/08/2012 4:32:42 PM - connecting
21/08/2012 4:32:43 PM - Info bpbrm(pid=5056) starting bpbkar32 on client        
21/08/2012 4:32:43 PM - connected; connect time: 00:00:01
21/08/2012 4:32:44 PM - Info bpbkar32(pid=5264) Backup started          
21/08/2012 4:32:44 PM - Info bptm(pid=6216) start           
21/08/2012 4:32:44 PM - Info bptm(pid=6216) using 262144 data buffer size       
21/08/2012 4:32:44 PM - Info bptm(pid=6216) setting receive network buffer to 1049600 bytes     
21/08/2012 4:32:44 PM - Info bptm(pid=6216) using 30 data buffers        
21/08/2012 4:32:45 PM - Info bpbkar32(pid=5264) CONTINUE BACKUP received.         
21/08/2012 4:32:46 PM - Info bptm(pid=6216) start backup          
21/08/2012 4:32:47 PM - Info bptm(pid=6216) backup child process is pid 4764.3204      
21/08/2012 4:32:47 PM - Info bptm(pid=4764) start           
21/08/2012 4:32:47 PM - begin writing
22/08/2012 2:40:43 AM - Error bptm(pid=4764) socket operation failed - 10054 (at child.c.1296)     
22/08/2012 2:40:43 AM - Error bptm(pid=4764) unable to perform read from client socket, connection may have been broken
22/08/2012 2:40:49 AM - Error bpbrm(pid=5056) could not send server status message      
22/08/2012 2:40:51 AM - Critical bpbrm(pid=5056) unexpected termination of client MSH-SV-LDR-CWS       
22/08/2012 2:40:53 AM - end writing; write time: 10:08:06
system call failed(11)

 

Please advice.

Comments 3 CommentsJump to latest comment

Mark_Solutions's picture

My first thought was that even though the backups are done over the SAN using the vSphere API your media server still needs to resolve the clients name to an IP address but then i noticed this:

21/08/2012 4:32:47 PM - begin writing
22/08/2012 2:40:43 AM - Error bptm(pid=4764) socket operation failed - 10054 (at child.c.1296)    
 

So it does look like it has been doing something for 10 hours before this crashed out

The 10054 error is network or communications related so tends to indicate a network or timeout issue.

The unexpected termination also suggests a possibility that something crashed

Has anything been logged on the vCenter server? Anything in the event logs of the media server (vm backup host) to indicate anything has crashed?

To pin it down some more logging will be required to see where it went wrong - bpbkar and bpbrm on the media server - possibly bpfis but it does look like it got past the snapshot phase and VxMS.

Let us know what you can find from that suggested above and post your findings so that we can help you further

Authorised Symantec Consultant

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

lowrider94's picture

Hi Neeraj,

I am using NBU7.5.0.4 MSDP Volume. I am trying to backup VM and I am getting exactly the same error . Have you found out the solution?