Chatta subito con l'assistenza
Chat con il supporto

NetVault Plug-in for VMware 11.2 - Release Notes

Resolved issues

Corrected an issue in which a restore failed if a virtual disk was missing. The plug-in creates the missing disk.

29631

Corrected an issue that prevented backups from completing on Linux® systems that use Ext3.

31582

Corrected an issue that prevented the restore of a Raw Device Mapping (RDM) disk to an alternate location or name.

31779

Corrected an issue that prevented successful completion of the phase 2 backup by NetVault Backup Plug-in for Data Copy (Plug-in for Data Copy).

31848

Corrected an error message. Message erroneously reported “Failed to prepare target filesystem for the restore.” Message improved to report “Failed to allocate space. There is not enough space on the disk.”

32025

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.

1714

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.

2371

If you select the Auto setting as the primary transport mode, during the backup of a virtual machine that has disks on SAN storage and 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 (network block device [NBD] or NBDSSL [encrypted]).

2394

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.

3131

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.

3340

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.

6598

(NVG-5474)

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.

13679

(VMW-157)

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

Workaround: Convert the template to a virtual machine.

13728

(VMW-202)

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.

21755

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

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 crashes.

21794

When a standalone 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.

22030

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.

22043

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.

24156

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 Hot-Add transport modes or decrease Read Block Size.

28815

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.

29043

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.

29795

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:

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 step merges the two folders created during the restore into a single folder.

 

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.

 

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.01TB, 3.99TB).

27742

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 http://kb.vmware.com/kb/1002403.

28921

To back up virtual machines that are protected by VMware vSphere Fault Tolerance (vSphere FT) with plug-in version 11.2 or later, your environment must use VMware® ESXi™ 6.0 build number 4192238 or later. If you use an ESXi host with an unsupported build, vSphere FT protection might become disabled during the snapshot process. This issue occurs because of an issue in earlier versions of the VMware ESXi host. This issue is more likely to occur when the virtual machine uses Windows 2008 or later as the guest OS and it uses the VMware Tools VSS provider to take quiesced snapshots. For more information, see VMware KB article 2145664.

31423, 32123

System requirements

Before installing Plug‑in for VMware®, ensure that your system meets the requirements outlined in the following table and in the Dell NetVault Backup Compatibility Guide available at https://support.quest.com.

Operating systems

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

NetVault Backup versions

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

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

Upgrade and compatibility

Plug‑in for VMware® 11.2 requires NetVault Backup 11.1or later. For complete supported-platform information, see the Dell 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 re-install 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.
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

32-bit

32-bit

 

 

 

 

 

Hybrid

 

 

 

 

 

64-bit

Itanium

N/A

N/A

N/A

N/A

N/A

64-bit

N/A

N/A

N/A

N/A

N/A

Hybrid

 

 

X

 

 

Pure64

 

 

 

 

X

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione