VM Backup failing with Error 13
Updated: 12 Apr 2012 | 19 comments
This issue has been solved. See solution.
12/22/2011 10:02:46 PM - requesting resource psddbu02-vcb-su
12/22/2011 10:02:46 PM - requesting resource ps23nb20.NBU_CLIENT.MAXJOBS.PSVI28HERM01
12/22/2011 10:02:46 PM - requesting resource ps23nb20.NBU_POLICY.MAXJOBS.VCB-Daily-NQ2
12/22/2011 10:02:46 PM - Info nbrb(pid=4608) Limit has been reached for the logical resource ps23nb20.NBU_POLICY.MAXJOBS.VCB-Daily-NQ2
12/22/2011 10:27:15 PM - granted resource ps23nb20.NBU_CLIENT.MAXJOBS.PSVI28HERM01
12/22/2011 10:27:15 PM - granted resource ps23nb20.NBU_POLICY.MAXJOBS.VCB-Daily-NQ2
12/22/2011 10:27:15 PM - granted resource MediaID=@aaaaj;DiskVolume=psddbu02-vcb-lsu;DiskPool=psddbu02-vcb-dp;Path=psddbu02-vcb-lsu;StorageServer=psddbu02.informatica.com;MediaServer=ps23nb09
12/22/2011 10:27:15 PM - granted resource psddbu02-vcb-su
12/22/2011 10:27:15 PM - estimated 0 Kbytes needed
12/22/2011 10:27:16 PM - started process bpbrm (3248)
12/22/2011 10:27:17 PM - connecting
12/22/2011 10:27:17 PM - connected; connect time: 00:00:00
12/22/2011 10:27:21 PM - begin writing
12/22/2011 10:32:18 PM - Error bpbrm(pid=3248) db_FLISTsend failed: file read failed (13)
12/22/2011 10:32:28 PM - end writing; write time: 00:05:07
file read failed(13)
Discussion Filed Under:
Comments
A little more details please
A little more details please ...
NBU versions, vSphere or VCB, vCenter / ESX versions and policy / snapshot settings
Also ESX datastore locations / type
Thanks
Authorised Symantec Consultant
Don't forget to give a "Thumbs Up" or mark as "Solution" if someones advice has helped you.
it's 5 minutes from connected to failure
You can try updating the Client Read Timeout on the client/media server in case the processing just isn't going fast enough....
PLEASE let us know all
PLEASE let us know all releveant info as per Mark's request....
I found this TN that could be relevant, but we need more detail: http://www.symantec.com/docs/TECH62391
Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows.
Handy NBU links
VCB was really dependent on
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.
Nothing has changed...
Check to see if bpbkar32.exe
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.
7.1.0.3 is the latest version currently available.
need to know...
Nothing has changed...
Answers for questions
Also taking help from marianne Post about the Technote .
It is a V Sphere ..attached is the Policy setting
Thanks,
Debashish
OS of backup host -
=> you HAVE to install eebinstaller.2105102.14.AMD64
Nothing has changed...
VCB
Disable Snapshot mount point (VCB).
Falti Manullang
"If this post has helped you, please vote or mark as solution"
That has no impact even if it
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.
Nothing has changed...
The error: db_FLISTsend
The error:
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 7.1.0.2 or 7.1.0.3 as they are several issues fixed around this area.
I see that you have quiece
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
Authorised Symantec Consultant
Don't forget to give a "Thumbs Up" or mark as "Solution" if someones advice has helped you.
Have made the changes
Thanks Guys , I had made changes as per suggestions from Mark and will try running the backup again to see how it goes.
Thanks,
Debashish
No Luck
I made the changes but the backup still fails with error 13 .
Thanks,
Debashish
I see that it fails after
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)
Authorised Symantec Consultant
Don't forget to give a "Thumbs Up" or mark as "Solution" if someones advice has helped you.
Raised a case with Symantec ( 415-938-226 )
Had to open a case with Symantec as still i am clueless after making all the changes still continues the error .
Thanks,
Debashish
Have you installed the VMWare
Have you installed the VMWare EEB yet?
(ET2105102)
Issues resolved and hotfix for NetBackup for VMWare backups
http://www.symantec.com/docs/TECH141502
Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows.
Handy NBU links
Haven't Tried with EEB
Thanks Marianne, Will download the EEB installer and update the forum how does it goes.
Thanks,
Debashish
Contact support to get the
Contact support to get the latest rollup.
71:
eebinstaller.2299772.3
701:
eebinstaller.2105102.14
700:
eebinstaller.2060693.11
Nothing has changed...
Would you like to reply?
Login or Register to post your comment.