NetVault Plug-in for Hyper-V 11.2

If your environment uses Windows Server 2008 R2 as the Hyper-V Server and you use the Rename feature during a restore, the recovery does not include network adapters that the VM backup included. After recovery is completed, use Hyper-V Manager to add the network adapters for the VM.

FB 17804

If your environment uses Windows Server 2008 R2 for Hyper-V Clustering, the number of parallel write streams that can be run is one. If you change the number, the plug-in prevents multiple backup streams from running simultaneously.

FB 17808

If you perform a file-level restore, do not use the Rename option in the Actions list for the VM node. Although the option is enabled, the plug-in ignores the Rename field and the restore completes with warnings.

FB 17824

If your environment includes Linux VMs and you perform a file-level recovery of a job that contains files with the same name but different capitalization, the job might complete with warnings. Because Windows is not case-sensitive, it does not recognize the distinction between the two files. All other selected files are recovered.

FB 17829

The plug-in does not correctly index compressed or sparse New Technology File System (NTFS) files on Windows Server. Because of this issue, you cannot recover compressed or sparse NTFS files during file-level recovery.

29043, FB 17836

The plug-in does not correctly index sparse files on extended (EXT) Linux file systems. Because of this issue, the sparse files cannot be recovered during file-level recovery.

Workaround: To recover sparse files, perform an image-level recovery.

27629, FB 17841

The plug-in does not support recovery of backups taken using versions 1.7 or 10.0.1.

Workaround: To recover sparse files from backups taken using version 1.7, perform an image-level recovery.

FB 17843

If your environment uses Windows Server 2012 R2 as the Hyper-V Server and you use the default Virtual Hard Disks directory to store the VM’s virtual drives, verify that all the VM’s disks reside in the same directory. If any disks reside elsewhere, recovery fails. This requirement is a limitation of the Hyper-V Import-VM cmdlet used in Windows PowerShell to create the VM during recovery.

Workaround for a failed recovery:

To locate the disks expected by Import-VM cmdlet, do one of the following:

•

Move all VHD or VHDX files from the Virtual Hard Disks directory to a different directory, and delete the Virtual Hard Disks directory.

•

Move all VHD or VHDX files to the Virtual Hard Disks directory.

To reflect the paths for any relocated VHD or VHDX files, update the VM’s .xml configuration file.

To import the VM, do one of the following:

•

In Hyper-V Manager, use Action > Import Virtual Machine.

•

In PowerShell, started with elevated permissions, run: Import-VM -Register -Path <pathToVMsXMLconfigFile>

FB 17846

If your VM relies on a storage pool created from virtual drives, the backup job fails.

Workaround: Turn off the VM, and run the backup job again.

FB 17851

System requirements

Before installing Plug‑in for Hyper‑V 11.2, ensure that your system meets the requirements outlined in the Quest NetVault Backup Compatibility Guide available at https://support.quest.com/technical-documents.

The plug-in requires installation of Windows PowerShell 3.0 or later. By default, Windows Server 2008 R2 includes PowerShell 2.0, which you must update to 3.0 or later. By default, Windows Server 2012, 2012 R2, and 2016 already include 3.0, 4.0, and 5.0, respectively.

Upgrade and compatibility

Plug‑in for Hyper‑V 11.2 requires NetVault Backup 10.0.5 or later. For complete supported-platform information, see the Quest NetVault Backup Compatibility Guide.


	CAUTION: The plug-in does not support recovery of backups taken using version 1.7. If you must be able to recover backups taken using version 1.7, do not upgrade to version 10.0.1 or later.