Please i need help resolving an issue i am currently experiencing. i configured virtual image backups successfully and got successfull backups (snapshot inclusive) but when i try initiating a restore, the back up virtual machine gets created on Vmware with some preliminary activities going on (disk lease etc) but later the VM gets deleted and the restore fails with VMware restore policy 2820. Pleasse find attached logs from recovery host to help in troubleshooting. Much appreciations for your previous assistance
I second Krutons.
I was never able to run a VM restore via SAN protocol.
In fact, I believe the manual states you need to do it with NBD (or NBDSSL) protocol.
That's not true, you can defintely restore over SAN. I just want to see if it works over NBD because if it does, it limits what the potential issue could be. Such as, the LUN on the datastore being offline.
yes NBD works but you know the issue with NBD when you are restoring a VM that is hugh. how do i troubleshoot the SAN failure cos obviously i now know its a SAN problem (zoning looks fine from SAN switch). i will check the storage for any discrepancies and revert. what logs can i share to determine or troubleshoot issue
AS long as the restore went successfully through NBD, you should probably look at the backup host permissions on the datastore, read-only access for backups but read&write for restores.
this error "cannot write data to socket, 10053" says all..
you should also check the tar & vxms logs on the vm backup host, the bpbrm on the media server.
Please how can i achieve this host permissions? is it via Vsphere client when assigning permissions to the account used in querying the vcenter?? please i need specifics as i want to be able to achieve SAN backups ASAP. Many thanks
Have you had a look at this Best Practice doc?
VMware Transport Modes: Best practices and troubleshooting
VM backup host is the server used to access the datastores, mostly it's the media server.
from your detailled status, look at the line : host to restore to (the name of the server is right there).
as Marianne posted, the link shows you the best practice, and especially -The line I was looking for :
you should look at this to know more about the account's permissions: