NetVault Plug-in for Hyper-V 10.5 - Release Notes

Resolved issues

The following is a list of issues addressed in this release.

 

Table 2. General resolved issues

Resolved issue	Issue ID
Corrected an issue in which recovering a VM in a Windows Server 2008 R2 environment appeared to succeed but a check of the Windows Event Viewer revealed the following message: Cannot load a virtual machine configuration. General access denied error.	FB 17332, FB 17335
Restored support for file-level backups and restores. To complete a file-level backup, process an image-level backup with the new Enable indexing for File Level Recovery option selected. Indexing lets you perform a subsequent file-level restore.	FB 17383
Corrected an issue that prevented a Windows Server® 2008 R2-based Hyper-V cluster from locating and backing up a VM on a remote host.	15117 (HYV‑124), FB 17635
Corrected an issue that prevented an individual VM from displaying correctly. If the VM was the only entry and displayed as part of a cluster or listed under localhost, the name of the VM was not displayed.	FB 17636
Corrected an issue that caused backups to fail when a cluster includes more than nine Cluster Shared Volumes (CSVs).	FB 17776

Known issues

The following is a list of issues, including issues attributed to third-party products, known to exist at the time of release.

 

Table 3. General known issues

Known issue	Issue ID
The network adapter configuration is occasionally lost during recovery of a VM. If this issue occurs, manually select the network adapter from the Hyper-V® Manager.	15132 (HYV‑22)
The Percentage Complete progress bar in the Monitor Job page is not currently populated with the appropriate progress of the job.	15160 (HYV‑48)
The plug-in does not currently handle VMs that have names ending with a whitespace.	15171 (HYV‑58)
The plug-in does not support Hyper-V® installations that have two or more VMs that share identical names.	15186 (HYV‑71)
If you are using the Hyper-V® Role for Windows Server® 2008 R2 with Simplified Chinese, French, German, and Korean, permission is not correctly granted during the VM recovery, which renders the VM unrecognizable by Hyper-V® Manager. To grant permission to the restored files manually, run the following command on all restored files, including .vhd, .avhd, .xml, .bin, and .vsv, for the VM. icacls <restore_file> /grant "NT VIRTUAL MACHINE/<VMID>":F /l Replace "NT VIRTUAL MACHINE" with the language equivalent. For example: icacls "C:\ProgramData\Microsoft\Windows\Hyper-V\VirtualMachine\2CAB416C-6B89-4B76-958A-CEAE95D33BAD.xml" /grant "Ordinateur Virtuel NT\2CAB416C-6B89-4B76-958A-CEAE95D33BAD":F /l The VMID is the GUID of the VM. Usually, the GUID is the same as the name of the .xml file. The "/l" is needed for symbolic-link files.	21572
The plug-in fails to mount an online virtual machine for backups if the VM name is too long. This length causes the “expose path,” formed by combining the paths to the plug-in Working Directory and the virtual disk files, to exceed 260 characters.	22818
If you are using the Hyper-V Role for Windows Server 2012 or 2012 R2 with a localized version of the NetVault Backup Server or Client, or both, manually remove the VM before initiating image-level recovery. Otherwise, recovery fails even though files are correctly restored to the Working Directory.	28005, FB 17369
Names of VMs targeted for backup cannot contain Unicode Characters. Backing up a VM that contains Unicode Characters in its name generates an “Error writing to backup media” message.	FB 17225
If you use a localized version of the plug-in, the following items are not translated: Options included in the Actions list and on the Plugin Options dialog box, and Messages listed on the Job Status or View Logs page.	FB 17344, FB 17346, FB 17351, FB 17361
If you restore a VM whose source has the same disk ID as the host, the VM displays an error (0xc000000e) and fails to start. Workarounds: • Run the BCDEdit command-line tool, and point the boot manager to the correct disk. • If the source VM is cloned from the same Virtual Hard Disk (VHD or VHDX), update the disk ID of the source VM. That is, change the disk ID inside each cloned VM.	FB 17393
Running a backup job that targets a VM whose operating system (OS) resides on a passthrough disk does not fail properly. This configuration is not supported; the backup job should fail and indicate that no disks were backed up. Instead of failing the job, the plug-in erroneously backs up configuration, .xml and recover_ctx.dat, files.	FB 17395
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 finished, 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 version 1.7, and it does not support file-level recovery of backups taken using version 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 or 2012 R2 as the Hyper-V Server and you use the default Virtual Hard Disks directory to store the VM’s virtual disks, make sure 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: 1 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 another directory, and delete the Virtual Hard Disks directory. • Move all VHD or VHDX files to the Virtual Hard Disks directory. 2 Update the VM’s .xml configuration file to reflect the paths for any relocated VHD or VHDX files. 3 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 virtual disks created from a storage pool, the backup job fails. Also, file-level indexing is not supported. Workaround: Power down the VM, and run the backup job again.	FB 17851
Whitespace — unallocated blocks of data — in Hyper-V-based dynamically expanding Virtual Hard Disks (VHDs/VHDXs) are not ignored during backup, which might impede backup performance. If your environment uses fixed VHDs/VHDXs, this issue should not affect it because the plug-in has always backed up the whitespace of fixed disks. If your environment uses Dell DR Series appliance or EMC® Data Domain® Boost (DD Boost™) as the backup target, you should see less impact on performance than with other backup targets. These targets use source-side deduplication technology, which handles whitespace more efficiently. If your environment uses tape, a virtual tape library (VTL), or NetVault SmartDisk as the backup target, you might see an impact on performance. The impact depends on how much whitepsace is present in the VHD/VHDX. Workaround: There is no workaround for this issue. If you use dynamically expanding disks and performance is affected, Dell recommends that you use Plug‑in for Hyper‑V- 10.0.1. For more information, see https://support.quest.com/kb/177612.	FB 17952

Software requirements

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

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 and 2012 R2 already include 3.0 and 4.0, respectively.

Upgrade and compatibility

Plug‑in for Hyper‑V® 10.5 requires NetVault Backup 10.0.5 or later. For complete supported-platform information, see the Dell 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.