Chat now with support
Chat with Support

NetVault Plug-in for VMware 11.1 - Release Notes

Resolved issues

Corrected an issue that prevented the plug-in from successfully restoring a virtual machine to an alternate ESX Server if the virtual machine was configured to use vNetwork Distributed Switch (vDS).


Addressed an issue that caused mount operations to fail if the virtual machines used Extensible Firmware Interface (EFI) firmware.


Corrected an issue that caused the Restore Files from Backup method to restore an invalid “.vmx” file if the virtual machine name contained non-ASCII characters. This issue was resolved in a previous release of the plug-in (version 10.5).



Corrected an issue in which virtual machine restores failed in a cluster setup if the original host was in maintenance mode.


Corrected an issue in which the plug-in did not automatically fall back to NBD mode when restoring Incremental or Differential Backups using SAN mode. This issue was resolved in a previous release of the plug-in (version 10.0.5).


Corrected an issue in which renaming during restore failed for a virtual machine if the virtual machine was previously renamed in vCenter Server.


Corrected an issue that caused file-level indexing to fail for virtual machines running CentOS 7 or RHEL 7 operating systems.


Corrected an issue that caused restore jobs to fail if the Rename and Relocate to Alternate Datastore options were used together.


Addressed an issue that caused backup failures during the snapshot removal phase.


Corrected an issue in which the excluded disks were backed up when you selected the folder node.


Corrected an issue that caused a restore job to fail after 15 minutes when restoring large Thick Provisioned Eager Zeroed disks.


Implemented changes to improve the performance of file-level indexing on EXT3 file systems.


Corrected an issue that caused mount operations to fail with the following error: Unable to GetVolumeMountPoints - Error code 20.


Corrected an issue that caused a backup job to fail during file-level indexing if you changed the Tmp directory for NetVault Backup or the Working Directory for the Plug‑in for VMware.


Implemented changes to create the symbolic link for ( in the correct location (/usr/lib64).


Known issues

Table 3. Known issues

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


Raw Disk Mapping (RDM) disks in virtual compatibility mode are restored to flat “.vmdk” files and not to the original RDM. The alternative is to omit these disks during a restore.


If you select the Auto setting as the primary transport mode, during the backup of a virtual machine that has disks on SAN storage as well as storage accessible only through the network, the NetVault Backup logs may report the transport mode incorrectly as “san” when the disk is opened in a network-based mode (nbd or nbdssl).


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 a large number of backups running simultaneously or your server is running under heavy load, modify the value for the [Custom:MountOperationTimeoutSecs] setting to avoid running into this situation.


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.


When you use the NetVault Backup Plug-in for Consolidation, the image-level backups of virtual machines are displayed on the Create Selection Set page, but you cannot consolidate these savesets.


When you browse a localized virtual machine from an X11 or Motif GUI, the encoding of the name can cause the display to be scrambled or to not appear at all.


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

Workaround: The workaround is to convert the template to a virtual machine.


To avoid file fragmentation, the Plug‑in for VMware pre-allocates disk space before restoring files to disk. On Linux-based systems, files that are larger than 50MB in size are not pre‑allocated full disk space. Such files are handled like sparse files and allocated disk space as needed during restore. If the disk does not have sufficient space to fully restore files that are larger than 50MB in size, the job fails when the disk runs out of space.


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


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


When a standalone VMware ESX or VMware® ESXi™ Server is added to the plug-in, a backup selection at a Resource Pool level does not back up any virtual machines in the resource pool.


When restoring the virtual machine disk and configuration files from an image-level backup, if you select an Incremental Backup with the Restore Files from Backup method, the plug-in only restores the Full Backup for the selected backup sequence.


Plug-in for VMware 2.6 issues:

Therefore, before removing the plug-in, you must take a copy of the libeay32.dll and ssleay32.dll files from the <NetVault Home>\bin directory, and restore them to the same directory after removing the plug-in. Otherwise, the NetVault Backup Service does not start.


When using the NBD transport mode, a large Read Block Size may prevent multiple backup processes from running at the same time.

Workaround: Use SAN or SCSI Hot-Add transport modes or decrease Read Block Size.


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.


If the Diagnose Virtual Machine method is unable to return any result within the timeout interval (five minutes), the Web Service process displays the following message: “Error: The remote machine: <Name of the NetVault Backup Server> is unavailable”

You can close this dialog box to continue the current operation. In the background, the Diagnose Virtual Machine method runs the cleanup process to remove any snapshot that it has created.


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


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


At the time of enabling CBT for a virtual machine, no snapshots must exist on it. For more information, see


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


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:

Unlocking is known to fail occasionally. This issue has been documented in the VDDK 5 release notes. For details, review the “EndAccess sometimes does not reenable migration after PrepareForAccess” section in the VDDK 5.0 Release Notes.


VDDK 5 issues:


When you restore a virtual machine that was previously renamed on a vCenter Server, the plug-in creates both the old and new virtual machines on the server.

Workaround: After restoring the backup, rename the virtual machine, and then, move the virtual machine to another datastore. This merges the two folders created during the restore into a single folder.


ESX/ESXi Servers do not support non-ASCII characters; this causes the restore jobs to fail if the virtual machine name uses multibyte characters. For more information, see


On a Windows 2012 virtual machine, data corruption may occur during or after a network copy operation. For more information, see


If the size of a virtual disk is 2TB or a multiple of 2TB, the disk is always opened in NBD mode instead of SAN. This issue only affects virtual machines that use hardware version 10 (vmx-10).

Workaround: Increase or decrease the size of the virtual disk (for example, to 2.01 TB, 3.99 TB).


When a virtual machine is cloned outside the vCenter Server, it may have the same UUID as the original virtual machine. If this cloned virtual machine is selected for a backup, the plug-in may back up the original virtual machine instead of the clone. To correct this issue, you must change the UUID of the cloned virtual machine. For more information about changing the UUID of a virtual machine, see


System requirements

Operating systems

For a list of supported OS distributions and versions, see the VDDK 6.0.2 Release Notes available at

NetVault Backup versions

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

For complete supported-platform information, see the NetVault Backup Plug-in Compatibility Guide available at

Upgrade and compatibility

Cannot browse mounted virtual machines after upgrading NetVault Backup: After installing the plug‑in, if you upgrade the NetVault Backup software, you must re-install the plug-in on that machine. Otherwise, you will be unable to open the Drives node of a mounted virtual machine for any new file‑level backups.
Restart the NetVault Backup Service if “nvvmwmount.exe” was running during upgrade: If the mount process “nvvmwmount.exe” was running during an upgrade from 2.x, restart the NetVault Backup Service on the client.
Select the correct installation package on Linux and Windows: NetVault Backup offers separate client‑only and server-only installation packages for Linux- and Windows-based systems. Both the server and the client packages are available in hybrid and pure 64-bit versions:
Hybrid server and client packages: The hybrid packages are intended for users who do not have a pure 64-bit-only requirement.
Pure 64-bit server and client packages: The pure 64-bit packages are intended for pure 64-bit operating systems. If you have a specific reason that you cannot use any 32-bit components (for example, you are using a Linux distribution that does not run 32-bit code), use these packages.
netvault-<RYYYYMMMDD>-vx.x.x.x-Server-{LinuxX86Hybrid|WindowsX86Hybrid}: Use this package to install or upgrade NetVault Backup Server on 32-bit or 64-bit systems.
netvault-<RYYYYMMMDD>-vx.x.x.x-Server-{LinuxX86Pure64|WindowsX86Pure64}: Use this package to install or upgrade NetVault Backup Server on pure 64-bit systems.
Table 6. Pure64 builds







































Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating