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

Added support for backing up virtual machines (VMs) whose names contain single quotation marks or apostrophes.

FB 17764

Corrected an issue that caused backups to fail when all clients contained in a cluster did not use the same installation path for the NetVault Backup Client software.

FB 18032

Corrected an issue that caused the plug-in to stop working when network access to a tape device was lost during a restore process.

27933, FB 18122

Corrected an issue that prevented browsing of inventory in a Windows Server 2008 R2 cluster.

FB 18201

Improved indexing for New Technology File System (NTFS) files when the size of the cluster exceeds the 4096 default.

FB 18210

Corrected an issue that caused backup jobs to stop responding after all tasks were finished.

FB 18268

Corrected an issue that caused backup jobs to stop responding intermittently and lose the message for PMGR_GIVE_SERVICE_A_TASK_RETURN_MSG.

FB 18269

Corrected parsing of the output from the Windows PowerShell script.

FB 17882

Corrected an issue that prevented browsing of VMs in a cluster when the number of VMs was significant.

FB 17883

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, or 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.

Replace "NT VIRTUAL MACHINE" with the language equivalent.

For example:

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 drive 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 (versions 10.5 and earlier of the plug-in) or specified location (version 11.1 and later).

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:

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 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 or 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:

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