NetVault Plug-in for VMware 12.2 - Release Notes

It is not possible to remove the Plug‑in for VMware 2.7 from a NetVault Backup instance installed on a 32-bit Windows machine. This issue is resolved as is.

DNVMWARE-1245

Corrected an issue that caused the "List of Virtual machine failed to backup" and "List of Virtual machine whose backup completed with warnings" to appear in same information window.

DNVMWARE-1746

Corrected an issue where file-level recovery failed when the destination folder did not exist after it was distributed to another proxy.

DNVMWARE-1838

Corrected an issue where backup failed with the error 'Job manager lost message channel unexpectedly' when a Unicode string pattern was added under Inclusion/Exclusion.

DNVMWARE-1889

Corrected an issue that caused the plug-in to exclude NetVault Backup Clients that were using Plug‑in for VMware 12.0 and NetVault Backup Clients that were managed by a server that used NetVault Backup Server 12.0.when using the Distributed Jobs feature for load balancing.

DNVMWARE-1901, DNVMWARE-1903

Corrected the issue of the localized version of the Plug‑in for VMware 12.1 user interface for Japanese not being fully translated.

DNVMWARE-1912

When restoring data to an alternate datastore, the plug-in does not verify whether the datastore is available. Verify that the datastore is valid and has sufficient disk space to accommodate the virtual machine.

DNVMWARE-18 (1714)

The configuration setting [Custom:MountOperationTimeoutSecs], which is stored in the vmware.cfg file, determines how long the plug-in process waits for the mount daemon to respond to a request. The default value is set to 600 seconds during a fresh install and 300 seconds during an upgrade. If the mount daemon is unable to complete a request within the specified interval, the virtual machine is left in a mounted state.

If you have many backups running simultaneously or your server is running under heavy load, modify the value for the [Custom:MountOperationTimeoutSecs] setting to avoid this issue.

DNVMWARE-505 (3131)

Virtual Disk Development Kit (VDDK) does not support non-UTF8 locales. On Linux-based clients that use non-UTF8 locales, the plug-in reports the error “Child Process died unexpectedly” and exits abnormally.

DNVMWARE-584 (3340)

You cannot back up virtual machine templates using the Plug‑in for VMware.

Workaround: Convert the template to a virtual machine.

DNVMWARE-713

(13728, VMW-202)

The file-level indexing process does not generate indexes for symlinks.

DNVMWARE-977 (21793)

The file-level indexing process does not treat hard links in any special way and generates index entries for them as if they are separate entities. When you restore a saveset that includes a hard link, the plug-in stops responding.

DNVMWARE-978 (21794)

When restoring NTFS sparse files, if the actual allocated size of a data run is smaller than the total size of the data run, the restored file might be corrupted.

DNVMWARE-1456 (29043)

Backups that have Active Block Mapping (ABM) enabled might stop working when memory is exceeded.

DNVMWARE-1584

The plug-in is unable to restore a virtual machine protected by VMware vSphere Fault Tolerance (vSphere FT) to an alternate VMware vCenter Server.

DNVMWARE-1691 (32398)

A restore fails to create a VM if the CD-ROM contains an ISO image backup.

Workaround: Create a dummy datastore with the same name as the datastore contained in the ISO image in the CD-ROM, and then run the restore job.

DNVMWARE-1695

Backing up a virtual machine succeeds if the Virtual Machine Disk (VMDK) fails to open and the Exclude data disks option is selected.

DNVMWARE-1696

If the inventory view is toggled, the selection set is grayed out on the Edit Set and Clone Set operations.

DNVMWARE-1900

ATTENTION: Aborting a restore to the original location deletes the original VM. This issue may result in data loss.

Workaround: Before you begin a restore to the original location, clone the original VM.

DNVMWARE-1906

If the same string is added for a VM pattern and a vSphere tag, then only one node gets backed up at a time.

DNVMWARE-1928

Tag-based backup fails when vCenter is configured with a custom port.

Workaround: Configure the vCenter to use a default-443 port.

DNVMWARE-1932

When backing up a powered on virtual machine through a VMware vCenter Server, the plug-in may fail to back up the “.nvram”, “.vmx”, and “.log” files. For more information, see http://kb.vmware.com/kb/1019286.

When a snapshot is created on a virtual machine that uses thin-provisioned disks, VMware vSphere (the client and the underlying disk library) identifies the disk as thick. For more information, see http://kb.vmware.com/kb/1020137.

At the time of enabling CBT for a virtual machine, no snapshots must exist on it. For more information, see http://kb.vmware.com/kb/1033816.

If an ESXi 5.x host is managed by a vCenter Server, the virtual machines should not be restored when connected directly to the ESXi host. This restriction is due to a feature introduced in vSphere 5. For more information, see http://www.vmware.com/support/developer/vddk/VDDK-500-ReleaseNotes.html#knownissues.

To prevent the migration of a virtual machine while its disks are being accessed for a backup or restore, the plug-in uses VDDK APIs to lock and unlock a virtual machine. This functionality is disabled by default. To enable it, see the user's guide for the plug-in. Currently, the locking functionality has the following known issues:

VDDK 5 issues:

On a Windows 2012 virtual machine, data corruption may occur during or after a network copy operation. For more information, see http://kb.vmware.com/kb/2058692.

CentOS and Red Hat Enterprise Linux (RHEL) 6.x:

If you are using either of these operating systems and versions and the Fallback Transport Mode is set to none, a VMware issue prevents the backup proxy from opening in HotAdd Transport Mode and causes it to open in network block device (NBD) mode instead.

DNVMWARE-1777

Operating systems

For a list of supported OS distributions and versions, see the VDDK 6.7 Release Notes.

NetVault Backup versions

The Plug‑in for VMware 12.2 requires NetVault Backup 12.1 or later.

For complete supported-platform information, see the Quest NetVault Backup Compatibility Guide available at https://support.quest.com/technical-documents.