Problems with restore of the full virtual machine
Restores of a full Hyper-V virtual machine may fail in the following cases.
The vhd or vhdx file(s) from the backup are not restored. You must select for the restore, or remove the current virtual machine and vhd or vhdx files from the destination server before you start the restore. If you remove the virtual machine but leave one or more vhd or vhdx files at the destination, the vhd or vhdx files from the backup are not restored.
The Hyper-V-VMMS writes the following warnings in the events log:
Event ID: 10127, sample event log message:
Unable to repair the network configuration for virtual machine'Virtual Machine Display Name'. The virtual machine may not have the same network connectivity as it did when the backup was taken. Inspect the network settings and modify them as necessary. (Virtual machine ID 0AD8DFCC-BDC0-4818-B6DF-7A1BA0A735BF)
Event ID: 10104, sample event log message:
One or more errors occurred while restoring the virtual machine from backup. The virtual machine might not have registered or it might not start. (Virtual machine ID "0AD8DFCC-BDC0-4718-B6DF-7A3BA2A735BF ")
The Hyper-V writer encountered a Network configuration error. The restored virtual machine can be started after you change the Network Adaptor configuration in the virtual machine settings.
The tar log contains a message similar to the following:
VssNode::doRestore: Current owner of VM .[<VM name> {<VM guid>}] is
[<current owner>] not this [<restore server>], To perform this restore either move
VM to this host [<restore server>] or Delete VM from Cluster, or perform redirected
restore at current owner.Note the following explanations:
For a restore to the original location: When the backup took place, the virtual machine was not HA, but now the virtual machine is HA. However, the node that owns the virtual machine is not the node from which the virtual machine was backed up.
For a redirected restore: The virtual machine is HA but the node that owns the virtual machine is not the restore server (the node that performs the restore).
See the recommended actions in the tar log message.
Note: In a redirected restore, the virtual machine is restored to a different location on the original Hyper-V server or to a different Hyper-V server. It is not restored to its original location on the original server.
A virtual machine may be configured on a Windows volume GUID. The following is an example of a Windows volume GUID:
\\?\Volume{1a2b74b1-1b2a-11df-8c23-0023acfc9192}\If you perform a redirected restore of a volume-GUID-based virtual machine and you back up the restored virtual machine, note: An attempt to do a redirected restore from the backup may fail. For example, consider a virtual machine that is configured on the following volume GUID:
\\?\Volume{1a2b74b1-1b2a-11df-8c23-0023acfc9192}\The virtual machine is then restored to a different volume GUID, such as:
\\?\Volume{2a3b70a1-3b1a-11df-8c23-0023acfc9192}\If the restored virtual machine is backed up and you do a redirected restore from the backup, the restore may fail.
To avoid this problem in a redirected restore, restore the virtual machine to a subdirectory of the volume GUID, such as to the following:
\\?\Volume{1a3b70a1-3b1a-11df-8c23-0023acfc9192}\REDIR_subdirectory\The NetBackup job Detailed Status tab contains a message similar to the following:
12/11/2009 17:35:58 - started process bpdm (pid=2912) ... the restore failed to recover the requested files (5) 12/11/2009 17:47:06 - Error bpbrm (pid=1348) client restore EXIT STATUS 185: tar did not find all the files to be restored
A message similar to the following appears in the eventvwr.msc file:
Failed to update the configuration with the new location of virtual hard disk 'F:\REDIR_VM\f\ADD_VHD\IDE_1_DISK.vhd' for virtual machine '<virtual_machine_name>': The requested operation could not be completed due to a virtual disk system limitation. Virtual disks are only supported on NTFS volumes and must be both uncompressed and unencrypted. (0xC03A001A). Remove the disk from the virtual machine and then attach the disk from the new location. (Virtual machine ID <virtual_machine_ID.)
This issue is due to a Microsoft limitation. See the following Microsoft link for more information:
http://technet.microsoft.com/en-us/library/dd440865.aspx
If sufficient permissions are not set on the destination file share, the restore completes with status 1, "The requested operation was partially successful." Messages similar to the following appear in the NetBackup job details log:
Unable to set VHD/VHDX metadata which includes alternate data streams and permissions. If VM does not boot, check the permissions of the VM's virtual disk files.
Note:
The VM's files are restored, but NetBackup was unable to restore the owner of the vhd or vhdx file(s).
For a fully successful restore, do the following:
Add permissions to the share and to the underlying file system where the data resides. The permissions must give Full Control to the Hyper-V server and to the Hyper-V cluster.
On the Hyper-V server to which the VM is to be restored: Make sure that the NetBackup Client Service is running as
Domain\Administratorand not as theLocalSystemuser account.
When these changes are complete, rerun the restore. The restore job should return status 0, "the requested operation was successfully completed."