Solved! Go to Solution.
Check to see if bpbkar32.exe is crashing on the VMware Backup Host. It could be several issues, I suggest upgrading to the latest NetBackup to address all known issues.
188.8.131.52 is the latest version currently available.
Also taking help from marianne Post about the Technote .
It is a V Sphere ..attached is the Policy setting
VCB was really dependent on the boot.ini to be able to do SFR aka Mapped Backups.
Note: If you upgrade a Windows 2003 machine to Windows 2008, sometimes the boot.ini does NOT get deleted and the next vstorage backup will go crazy. Difficult to identify if you have never run into that issue before.
That has no impact even if it is selected. Still... make sure VCB is NOT installed anymore on the backup host. Check add/remove programs, task manager (vmount2) and make sure that c:\program files*\vmware\vmware consolidated backup host is gone.
db_FLISTsend failed: file read failed (13)
Means that bpbrm send some information about the data to the master server bpdbm and it did not like it. In most cases, this is the Volume Recognition is failing on the Virtual Machine. It is strongly advise that you upgrade from 7.0.1 to 184.108.40.206 or 220.127.116.11 as they are several issues fixed around this area.
I see that you have quiece disabled - are you sure you want this setting as the data may not be consistent.
I would tidy up the snapshot options first:
Ensble quiece, remove the VCB entries, select a data transfer method rather than leave it as "Try All"
Make sure that VMTools is up to date on the host
Increase the client read timeout for the Media Servers to 1800
Try again and let us know how it goes
(but update everything as soon as you can)
Hope this helps
I made the changes but the backup still fails with error 13 .
I see that it fails after just 3 minutes this time so that tends to rule out the timeout issues (unless you have short client read timeouts set)
If this host fully resolvable (ping / reverse DNS lookup etc.) from the VMWare Backup Host? Although it doesnt back it up over the network it does do a resolution check first.
If this is not the case we need some logs now so set up the following, re-run the failing backup and post the logs
install_path\NetBackup\logs\bpbrm on the Media server
install_path\NetBackup\logs\bptm on the Media server
install_path\NetBackup\logs\bpfis on the VMWare Backup Host (Media Server)
install_path\NetBackup\logs\bpcd on the VMWare Backup Host (Media Server)
install_path\NetBackup\logs\bpbkar on the VMWare Backup Host (Media Server)