Showing results for 
Search instead for 
Did you mean: 

VMware backup status 13 after snapshot

Level 4

Hi all,

I am experiencing a strange problem on a vm host backup wich is failing in status file read failed(13) after successfully create the snapshot.



8/9/2011 12:19:58 PM - granted resource PDDO-digimqbkpure01_digimqbkmed01
8/9/2011 12:19:58 PM - estimated 18260298 Kbytes needed
8/9/2011 12:20:00 PM - started process bpbrm (13846)
8/9/2011 12:20:03 PM - connecting
8/9/2011 12:20:04 PM - connected; connect time: 00:00:01
8/9/2011 12:20:25 PM - begin writing
8/9/2011 12:21:00 PM - Error bpbrm(pid=13846) socket read failed: errno = 104 - Connexion ré-initialisée par le correspondant 
8/9/2011 12:21:00 PM - Error bptm(pid=13854) system call failed - Connexion ré-initialisée par le correspondant (at child.c.1296)  
8/9/2011 12:21:01 PM - Error bptm(pid=13854) unable to perform read from client socket, connection may have been broken 
8/9/2011 12:21:02 PM - Error bptm(pid=13847) media manager terminated by parent process       
8/9/2011 12:21:16 PM - Info digimqbkmed01(pid=13847) StorageServer=PureDisk:digimqbkpure01; Report=PDDO Stats for (digimqbkpure01): scanned: 1 KB, stream rate: 3,30 MB/sec, CR sent: 0 KB, dedup: 100,0%, cache hits: 0 (0,0%)
8/9/2011 12:21:17 PM - Error bpbrm(pid=13846) could not send server status message       
8/9/2011 12:21:22 PM - end writing; write time: 00:00:57
file read failed(13)


The strange is that only this vm host has this problem and it used to run fine. The others are running fine in the same policy and same esx :


Perform off-host backup = VMware backup host

Options = VM display name / Mapped full VM backup / Transfert Try all types / Quiesced disabled / Exclude unused and deleted blocks enabled 


Does someone has an idea please ?



Master Netbackup 7.0 WinServer 2003 Enterprise

MediaServer NB 7.0 Linux RHEL AS 4.5

Backup-Host NB 7.0 WinServer 2003 Enterprise

VCenter 4.0.0 ESX 4.0.0

VM host WinServer 2003 Standart


Level 6
Partner    VIP    Accredited Certified

You might want to upgrade to 7.0.1... 

There is a  downloadable hotfix for this problem in NBU 7.0.1 :   (This link is for version 5 of the EEB. We logged a call for status 13 and was given version 8 of the EEB)    

Please also see this post:

Level 4

Hi Marianne,

Thanks for your post.

I don't think that it is the same problem than dunno's post because the snapshot is successfully created and removed after the error.

But the hotfix you gave me also talks about "NBU is using deprecated API's in vmwaretools"


I have a case opened at symantec support, hope they'll confirm your suggestion.

I'll keep you inform of the solution.

Thanks again.



Level 6
Employee Certified

Try to disable exclude white spaces also is your backup host 32bit or 64bit?

Does it only fail with that VM?

Level 4

Anyone have a solution?

How I disable exclude white spaces to test?

Level 6
Employee Certified

Open up the VMware policy

=> click on options

=> disable exclude whites spaces

Level 6
Partner Accredited

Most of the time, error messages for VMWare VM backup are not significant...

The only way I found to understand why the backup fail is to set a very high level of logging !

Warning : logs under C:\Program Files\Common Files\VERITAS\VxMS\Logs and installpath\NetBackup\logs\bpbkar take a lot of space !


I use the following logging levels in VMWare environment :

Bpbkar log level level set to 5 on the client.

HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\VxMS\Logging set to 7580 hexadecimal

DWORD registry value "VIXLog" under the following registry key set to 1


DWORD registry value "vmcloglevel" under the following registry key set to 6


 VxMS logs will be collected at: C:\Program Files\Common Files\VERITAS\VxMS\Logs

The bpbkar log is under installpath\NetBackup\logs\bpbkar