VMware backups fail with a bpbkar fault due to nbuVmwareTools.dll, resulting in a status code 13 (file read failed) reported.
9/10/2012 10:25:10 AM - Error bpbrm(pid=13456) socket read failed, An existing connection was forcibly closed by the remote host. (10054)
9/10/2012 10:25:14 AM - Error bpbrm(pid=13456) could not send server status message
9/10/2012 10:25:14 AM - Info bpbkar32(pid=0) done. status: 13: file read failed
9/10/2012 10:25:14 AM - end writing; write time: 00:00:19
file read failed(13)
Event Viewer (Application):
Response: Not available
Cab Id: 0
These files may be available here:
Rechecking for solution: 0
Report Id: cd07055f-e550-11e1-91a3-0018fe2e93aa
Report Status: 4"
Error 8/13/2012 10:11:40 AM Application Error 1000 (100)
"Faulting application name: bpbkar32.exe, version: 7.500.312.605, time
Faulting module name: nbuVmwareTools.dll, version: 126.96.36.199, time stamp:
Exception code: 0xc0000005
Fault offset: 0x0000000000333bb2
Faulting process id: 0x1478
Faulting application start time: 0x01cd795d57a2c945
Faulting application path: D:\Program Files\Veritas\NetBackup\bin\bpbkar32.exe
Faulting module path: D:\Program Files\Veritas\NetBackup\bin\nbuVmwareTools.dll
This behavior is caused when NetBackup is unable to obtain the status of one of the disks owned by the client being backed up.
The formal resolution for this issue (Etrack 2902616) is included in the following release:
- NetBackup 7.5 Maintenance Release 5 (188.8.131.52)
NetBackup 184.108.40.206 is now available - please access the Related Article linked below for download and README information.
This issue has been reported on NetBackup 7.5.0.x (through 220.127.116.11)