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.

netbackup 7.5 - vm backup - unexpected termination of client - system call failed (11)

Created: 28 Feb 2013 • Updated: 28 Feb 2013 | 4 comments
This issue has been solved. See solution.

Hi,

Windows 2008 R2, Netbackup 7.5.0.5, PureDisk

when backuping vm's the job failed - system call failed(11)

 MS-Windows file & folder backups run fine

p.s. 3 days early all backups runs just fine

please help

2/28/2013 3:46:41 PM - Info nbjm(pid=2576) starting backup job (jobid=3532) for client GDM-DB-POSDS_CLEAR_DB, policy 123, schedule Full 

2/28/2013 3:46:41 PM - estimated 0 Kbytes needed

2/28/2013 3:46:41 PM - Info nbjm(pid=2576) started backup (backupid=GDM-DB-POSDS_CLEAR_DB_1362052001) job for client GDM-DB-POSDS_CLEAR_DB, policy 123, schedule Full on storage unit gdm-backup

2/28/2013 3:46:42 PM - Info bpbrm(pid=5572) GDM-DB-POSDS_CLEAR_DB is the host to backup data from    

2/28/2013 3:46:42 PM - Info bpbrm(pid=5572) reading file list from client       

2/28/2013 3:46:42 PM - Info bpbrm(pid=5572) starting bpbkar32 on client        

2/28/2013 3:46:42 PM - started process bpbrm (5572)

2/28/2013 3:46:42 PM - connecting

2/28/2013 3:46:42 PM - connected; connect time: 00:00:00

2/28/2013 3:46:48 PM - Info bpbkar32(pid=1712) Backup started          

2/28/2013 3:46:48 PM - Info bptm(pid=6236) start           

2/28/2013 3:46:48 PM - Info bptm(pid=6236) using 262144 data buffer size       

2/28/2013 3:46:48 PM - Info bptm(pid=6236) setting receive network buffer to 1049600 bytes     

2/28/2013 3:46:48 PM - Info bptm(pid=6236) using 16 data buffers        

2/28/2013 3:46:50 PM - Info bptm(pid=6236) start backup          

2/28/2013 3:46:50 PM - begin writing

2/28/2013 3:47:03 PM - Info bpbkar32(pid=1712) bpbkar waited 0 times for empty buffer, delayed 0 times.  

2/28/2013 3:47:03 PM - Info bptm(pid=6236) waited for full buffer 1 times, delayed 785 times   

2/28/2013 3:47:03 PM - Info bptm(pid=6236) EXITING with status 90 <----------       

2/28/2013 3:47:06 PM - Info gdm-netbackup.gdm.ge(pid=6236) StorageServer=PureDisk:gdm-netbackup.gdm.ge; Report=PDDO Stats for (gdm-netbackup.gdm.ge): scanned: 2 KB, CR sent: 0 KB, CR sent over FC: 0 KB, dedup: 100.0%

2/28/2013 3:47:06 PM - Error bpbrm(pid=5572) could not send server status message      

2/28/2013 3:47:06 PM - Critical bpbrm(pid=5572) unexpected termination of client GDM-DB-POSDS_CLEAR_DB        

2/28/2013 3:47:06 PM - Info bpbkar32(pid=0) done. status: 11: system call failed      

2/28/2013 3:47:06 PM - end writing; write time: 00:00:16

system call failed(11)

Operating Systems:

Comments 4 CommentsJump to latest comment

rkavtiashvili@gmail.com's picture

huh,

I found the problem,

don't know how & why, but in registry missed some information:

[HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\VxMS]
"InstallDir64"=""
"Logging"=dword:00000000
"OldInstallDir"=""

and i put the install path

[HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\VxMS]
"InstallDir64"="C:\\Program Files\\Common Files\\VERITAS\\VxMS\\"
"Logging"=dword:00000000
"OldInstallDir"="C:\\Program Files\\Common Files\\VERITAS\\VxMS\\ "

all jobs works fine

SOLUTION
Jaykullar's picture

Can you tell us a bit more about your configuration? Have you manually added clients or are you using a query? Are you backing up over the Network or does the VM backup host have the LUNs presented to it?

Do the following directories and dlls exist?

C:\Program Files\Common Files\VERITAS\VxMS

C:\Program Files\Common Files\VERITAS\VxMS\Map

C:\Program Files\Common Files\VERITAS\VxMS\Shared

Is your media server added as a backup host?