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 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. |
|
Implemented changes to improve the performance of file-level indexing on EXT3 file systems. |
|
Implemented changes to create the symbolic link for libexpat.so.1.5.2 (libexpat.so.0) in the correct location (/usr/lib64). |
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. |
|
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. |
|
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. |
|
The file-level indexing process does not generate indexes for symlinks. |
|
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. |
|
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. |
For a list of supported OS distributions and versions, see the VDDK 6.0.2 Release Notes available at https://www.vmware.com/support/developer/vddk/vddk-602-releasenotes.html. | |
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 https://support.quest.com/. |
• |
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. |
NOTE: X = Compatible |
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center