Corrected an issue that prevented the Quiesce VM for snapshot option from being saved in the Backup Preferences dialog box and applied to all backup jobs. |
|
Corrected an issue that made disks that were excluded from a backup available for restore. |
|
Raw Device 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. |
|
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. |
|
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: Convert the template to a virtual machine. |
|
The file-level indexing process does not generate indexes for symlinks. |
|
When using the NBD transport mode with VMware vSphere 5.1, a large Read Block Size may prevent multiple backup processes from running at the same time. Workaround: Use SAN or SCSI HotAdd 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. |
|
Backups that have Active Block Mapping (ABM) enabled might stop working when memory is exceeded. |
|
Backing up a virtual machine succeeds if the Virtual Machine Disk (VMDK) fails to open and the Exclude data disks option is selected. |
|
Installing an update of the plug-in puts the VMware Vstor2 MntApi driver into an inconsistent state. If you are using a Windows-based proxy server, restart the server after you remove a VDDK. If you try to install or remove the VMware Vstor2 MntApi driver without restarting the server, you might encounter an error. For more information, see http://pubs.vmware.com/Release_Notes/en/developer/vddk/65/vsphere-vddk-65-release-notes.html. Before installing the latest version of the plug-in, complete the following steps: |
|
For a list of supported OS distributions and versions, see the VDDK 6.7 Release Notes. | |
The Plug‑in for VMware 12.0 requires NetVault Backup 11.4.5 or later. For complete supported-platform information, see the Quest NetVault Backup Compatibility Guide available at https://support.quest.com/technical-documents. |
Plug‑in for VMware 12.0 requires NetVault Backup 11.4.5 or later. For complete supported-platform information, see the Quest NetVault Backup Compatibility Guide.
• |
Cannot browse mounted virtual machines after upgrading NetVault Backup: After installing the plug‑in, if you upgrade the NetVault Backup software, you must reinstall the plug-in on that machine. Otherwise, you cannot 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. |
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center