Chat now with support
Chat mit Support

NetVault Plug-in for VMware 10.0.5 - Release Notes

Known issues


Table 4. Known issues
Workaround: Restore the virtual machine files to a local directory, and then restore the virtual machine to a remote server using VMware Converter.
The “.nvram” and “.vmx” files must reside in the same directory. Otherwise, you must manually edit the file path for the “.nvram” file after restoring the data.
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.
Workaround: The workaround is to convert the template to a virtual machine.
Workaround: Restore the virtual machine to the root resource pool by specifying “/” in the Allocate to Different Resource Pool box. After the restore completes, manually move the virtual machine to the desired resource pool using the vSphere Client.
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.
If the virtual machine name includes non-ASCII characters, the Restore Files from Backup method restores an invalid “.vmx” file, which cannot be used to create a virtual machine using the VMware Converter utility. For such virtual machines, you must manually create a new virtual machine using the restored “.vmdk” files.
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.
Workaround: Set the transport mode manually to NBD.
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 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.
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.
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.
Workaround: Increase or decrease the size of the virtual disk (for example, to 2.01 TB, 3.99 TB).

System requirements


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

Upgrade and compatibility


Deployment on ESX Service Console is not supported: The Plug‑in for VMware cannot be installed on the ESX Service Console; this type of installation is not supported by VMware. To upgrade deployments that have the Plug‑in for VMware 1.x installed on the ESX Service Console, you must install the plug-in on the NetVault Backup Server or Client. The license would be reissued in such cases.
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.
“Use Volume Shadow Copy Service” option is not supported: The option “Use Volume Shadow Copy Service” is not supported by the Plug‑in for VMware 2.x and later. This check box is deselected by default. If you select this check box in the Backup Preferences dialog box, the backup jobs fail with the error “Failed to quiesce the guest within VM.”
Select the correct installation package on Linux: Starting with 10.0, NetVault Backup offers separate client-only and server-only installation packages for Linux-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 (LinuxX86HybridServer and LinuxX86Hybrid) are intended for Linux users who do not have a pure 64-bit-only requirement.
Pure 64-bit server and client packages: The pure 64-bit packages (LinuxX86Pure64Server and LinuxX86Pure64) packages are intended for pure 64-bit Linux distributions. 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.
LinuxX86HybridServer: Use this package to install or upgrade NetVault Backup Server on 32- or 64-bit Linux systems.
LinuxX86Hybrid: Use this package to install or upgrade NetVault Backup Client on 32- or 64-bit Linux systems.
LinuxX86Pure64Server: Use this package to install or upgrade NetVault Backup Server on pure 64-bit Linux systems.
LinuxX86Pure64: Use this package to install or upgrade NetVault Backup Client on pure 64-bit Linux systems.
Table 7. Pure64 builds

Product licensing


2
In the NetVault Backup Clients list, select the client, and click Manage.
3
On the View Clients page, note the machine ID exactly as it appears in the Client Summary table.
1
In the Navigation pane, click Guided Configuration, and then on the NetVault Configuration Wizard page, click Install Licenses.
2
In the NetVault Backup Clients list, select the client on which you want to install the license key, and click Next.
3
In the Enter the license key string box, type or copy and paste the license key, and click Apply.
2
In the NetVault Backup Clients list, select the client on which you want to install the license key, and click Manage.
3
On the View Clients page, click Install License.
4
In the Install License dialog box, type or copy and paste the license key, and click Apply.
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen