Best practices
It is recommended the following for NetBackup for Hyper-V:
When creating virtual machines, use the same name for the VM's host name and display name. If the NetBackup policy's option is changed, the existing entries on the NetBackup policy Clients tab still work.
In a virtual desktop infrastructure where VMs share a common parent disk, do the following when restoring a VM to its original location: Restore the VM's differencing disk but not its parent disk. Make sure that the parent disk already exists on the same restore path.
On the Restore Marked Files dialog, under List of backed up files, clear the check mark from the parent disk. In the following example, the parent disk
vm1.vhdxis unselected:Note:
If you restore the parent disk to the original location, the other linked VMs that share the parent disk cannot be used. Their connection to the parent disk is lost. Instead, restore the differencing disk without the parent disk and make sure that the parent disk already exists on the same restore path. Otherwise, the restore fails because the parent disk does not exist.
Note:
This issue does not apply when you restore the VM to an alternate location. As long as no other VMs at the restore location share the parent disk, you can restore the parent disk along with the differencing disk.
Caution:
For restore to the original location: If you restore the parent disk and edit the linked VMs by reconnecting their differencing disks to the restored parent disk, VM data may be lost.
More information is available on NetBackup and Hyper-V.
For a list of supported Hyper-V servers, see the appropriate version of the NetBackup Software Compatibility List available from the following location:
For additional details on NetBackup support for Hyper-V, see the following:
A wide variety of information is available at Microsoft TechNet.
For example, refer to the Hyper-V Getting Started Guide: