This is a known issue with Symantec Backup Exec 2010 R3. For more information, see the Symantec Knowledge Base article
TECH184653.
Note: The preceding link was correct as of April 17, 2012. If you find the link is broken, provide feedback and a VMware employee will update the link.
To resolve this issue, contact Symantec support.
To work around this issue:
Warning: This workaround is not supported by VMware. VMware recommends you to contact Symantec for a supported workaround.
- Instead of selecting the ESX/ESXi host as target for the restore operation, select a directory on the Backup Exec server. The restore using a directory as the target completes successfully.
Note: You can set up an NFS share that is accessible by both the ESX/ESXi hosts and the Backup Exec server and use this as the target for the restore from within Backup Exec. In this case, you need not copy the files to the ESX/ESXi hosts and instead add them to inventory from the NFS share.
- After the files are restored, copy the files to the required directory on the ESX/ESXi host using the datastore browser or SCP/SFTP.
- Add the virtual machine back to the inventory using the datastore browser. For more information, see Registering or adding a virtual machine to the inventory (1006160).