Cannot restore a VM - 2 VMDK files named the same; on different LUN's
I am attempting a restore of a vSphere 4.0 VM using NetBackup Enterprise Server v7.0.1
In production, the server has 2 VMDK files residing on two different LUN's (on 2 different SAN's).
Both of these LUN's are VMFS and are presented to my backup server that does the backups (my media server).
Thus, their vmdk names are the same.
Is this an issue when restoring?
Error Log:
2/22/2011 2:39:05 PM - Error bpbrm(pid=1588) socket read failed, An existing connection was forcibly closed by the remote host. (10054)
2/22/2011 2:39:05 PM - Error bptm(pid=3160) cannot write data to socket, 10054
2/22/2011 2:39:10 PM - Error bpbrm(pid=1588) client restore EXIT STATUS 13: file read failed
2/22/2011 2:40:08 PM - restored image SERVER_1298044860 - (the restore failed to recover the requested files(5)); restore time 00:11:10
2/22/2011 2:40:08 PM - end Restore; elapsed time: 00:11:10
the restore failed to recover the requested files(5)
Comments
Try using the NetBackup 7.0.1 Hotfix for VMware backups
This might help.
http://www.symantec.com/business/support/index?pag...
I ran into this error before when I defined the short name of the esx host in the NetBackup credentials and the hostname for the esx-host was a FQDN name. I ended up creating a host file entry on the NetBackup VMware backup host with the esx host IP address with the esx host fqdn, so that the actual hostname of the esx-host matched on both the NetBackup and VMware side. Now, I use the FQDN name of the esx servers when defining their credentials in NetBackup.
Would you like to reply?
Login or Register to post your comment.