VMware

VMware Consolidated Backup 1.5 Update 2 Release Notes

VMware Consolidated Backup 1.5 Update 2 | 11 March 2010 | Build 226297

Last Document Update: 13 July 2010

New: VMware has extended the end of availability timeline for VCB, and has added VCB support for vSphere 4.1. VMware will continue to support VCB 1.5 Update 2 for vSphere 4.1 and its subsequent update and patch releases through the end of their lifecycles. Support is extended in accordance with the VMware Lifecycle Product Matrix for the VMware Infrastructure 3 platform. New major or minor versions of the vSphere platform beyond vSphere 4.1 will not be supported with VCB.

What's in the Release Notes

The release notes cover the following topics.

What's New in This Release

This release of VCB 1.5 Update 2 addresses several issues. See the Resolved Issues section for information.

Top of Page

Prior Releases of VMware Consolidated Backup

Features and known issues from VCB 1.0.3 Update 1, VCB 1.1, VCB 1.1 Update 1, VCB 1.5, and VCB 1.5 Update 1 are described in the release notes for each release.

  • VCB 1.0.3 Update 1 (HTML)
  • VCB 1.1 (PDF)
  • VCB 1.1 Update 1 (HTML)
  • VCB 1.5 (HTML)
  • VCB 1.5 Update 1 (HTML)

Top of Page

Upgrading from Previous Versions of VCB 1.5 to VCB 1.5 Update 2

To upgrade from VCB 1.5 or VCB 1.5 Update 1 to VCB 1.5 Update 2:

  1. Download the vmware-vcb-226297.exe from the VMware Web site or from the vSphere CD to a directory in the VCB Proxy. VCB Proxy is a physical or virtual machine running Microsoft Windows Server 2003 or Microsoft Windows 2008, Consolidated Backup, and third-party backup software.
  2. Double-click vmware-vcb-226297.exe and follow the on-screen instructions to complete the upgrade.

To verify the upgrade in Microsoft Windows 2003:

  1. In the VCB Proxy, go to Control Panel > Add or Remove Programs, and click VMware Consolidated Backup Framework.
  2. Click Click here for support information to view the version. It should be 1.5.0.5584 build-226297.

To verify the upgrade in Microsoft Windows 2008:

  1. In the VCB Proxy, go to Control Panel > Programs and Features, and click VMware Consolidated Backup Framework.
  2. From View Menu, click Details, select Version checkbox , and click OK to view the version. It should be 1.5.0.5584 build-226297.

Top of Page

ESX, vCenter Server, and VCB Compatibility

VCB 1.5 Update 2 is compatible with the following combinations of ESX and vCenter Server:

  • New: ESX 4.1 with vCenter Server 4.1
  • New: ESX 4.0 Update 1 and Update 2 with vCenter Server 4.0 Update 1 and Update 2
  • ESX 4.0 with vCenter Server 4.0
  • ESX 3.5 Update 5 with vCenter Server 2.5 Update 5 and Update 6
  • ESX 3.0.3 Update 1 with VMware VirtualCenter 2.5 Update 5 and Update 6

For the latest information, refer the vSphere Compatibility Matrix.

Top of Page

Installation Notes

Refer the Virtual Machine Backup Guide for instructions on installing and configuring VCB 1.5 Update 2.

Top of Page

Resolved Issues

  • New: Snapshot creation of Windows Server 2008 or Windows Server 2008 R2 virtual machines fails during application-level snapshot quiescing for combination of IDE and SCSI disks

    In previous releases, with the default snapshot quiescing happening at application level, snapshot creation of Windows 2008 or Windows 2008 R2 virtual machines that had combination of IDE and SCSI disks used to fail with a Cannot create a quiesced snapshot because the create snapshot operation exceeded the time limit for holding off I/O in the frozen virtual machine error.

    Now, when a Windows 2008 or Windows R2 2008 virtual machine has a combination of IDE and SCSI disks attached to it, snapshot quiescing is performed only at the file-system level. The issue is fixed in this release.

  • Backup of virtual machines with vcbmounter -M1 takes longer duration

    Performing backup of virtual machines containing .vmdk files greater than 50GB with the vcbmounter -M1 (monolithic export) command takes longer duration compared to vcbmounter -M0 command. The issue is fixed in this release.

  • Full virtual machine backup through vcbMounter command fails with an error message

    When you try to take a full virtual machine backup by using the vcbMounter command with vCenter Server, the backup operation fails with a Could not back up config file error message. The issue is fixed in this release.

  • Incorrect error message is displayed during backup of virtual machines in NBD mode

    When performing backup of virtual machines using NBD mode and if there is network loss during a full virtual machine backup mount, an incorrect error message invalid NBD error code is displayed. In this release, the error message is corrected to Failed to export the disk: Probably network disruption.

Top of Page

Known Issues

† denotes the issues documented in previous releases

  • New: VCB file-level mount of Windows Server 2008 using NBD transport mode fails with an Disk library failed (NBD_ERR_GENERIC) error

    When the disk.EnableUUID parameter in the virtual machine settings is set to True on a Windows Server 2008 virtual machine, the VCB file-level mount using NBD transport mode will either fail with a Disk library failed (NBD_ERR_GENERIC)error or might stop responding, and the vcbMounter command does not run.

    Workaround: Set the disk.EnableUUID parameter in the virtual machine settings to False by performing the following steps:

    a) Power off the Windows Server 2008 virtual machine through vSphere Client.
    b) Click Settings > Options >General > Configuration Parameters.
    c) Set disk.EnableUUID to False.
    d) Save the settings.
    e) Power on the virtual machine.

  • New: VCB fails to perform hot-add operations on virtual machines running on ESX 4.1 hosts

    Error messages similar to the following might be displayed when VCB fails to perform hot-add operations on a virtual machine:

    2010-03-12 17:21:06.300 'vcbMounter' 928 info] Successfully hot-added disks to VM.
    [2010-03-12 17:21:21.456 'vcbMounter' 928 info] Get new device attempt 0 failed
    [2010-03-12 17:22:51.737 'vcbMounter' 928 error] Error: Could not locate device nodes for new disks.
    [2010-03-12 17:22:51.737 'vcbMounter' 928 error] An error occurred, cleaning up...

    The hot-add operation does not work when Windows proxy is a virtual machine that resides on an ESX 4.1 host. If the virtual proxy is on an ESX 4.1 host, no backups are performed using hot-add operation, irrespective of ESX version the virtual machines reside on. This issue does not impact physical proxy servers because hot-add operations cannot be performed on them.

    Currently, there is no workaround for this issue.

  • New: Backup images of Windows Server 2008 R2 and Windows 7 operating systems are not supported with VCB 1.5 Update 2

    VMware Converter 4.0.1 does not support restoring the backup images of Windows Server 2008 R2 and Windows 7 guest operating systems and hence there is no way to restore backups.

    Currently, there is no workaround for this issue.

  • Running vcbRestore command to restore VCB backup fails with error (KB 1018768)
  • VCB does not support virtual machines with bootable SCSI disks and IDE disks

    VCB generates an exception when file-level backups of virtual machines are taken after attaching an IDE disk in addition to the already installed bootable SCSI disk that contains the guest operating system. No errors are generated when a full backup of a virtual machine is taken. However, after restoring the backup of the virtual machine and powering it on, because the first bootable disk is IDE, the guest operating system does not boot.

    To work around this issue, manually select the first bootable disk as the SCSI disk in the BIOS of the virtual machine.

  • Hot-Add transport mode fails to take backup of virtual disks

    On a Windows proxy server, hot-add transport mode fails to take backup of virtual disks belonging to different datastores.

    Currently, there is no workaround for this issue.

  • Three transport modes of VCB support on IDE disk

    On IDE disks, SAN, nbd, and nbdssl transport modes are supported, while hot-add transport mode is not. When a virtual machine is backed up by using hot-add transport mode in VCB 1.5 Update 1, the backup operation fails with a Cannot use hot-add to transport to mount Virtual Machines with non-SCSI disks error.

  • VCB file-level mount fails when the guest operating system is not installed on the first virtual hard disk

    When VCB tries to take a file-level backup on a virtual machine with the Windows operating system not installed on the first virtual hard disk of the virtual machine, the backup operation fails with a Cannot query guest operating information. The mount directory is invalid. error.

    Currently, there is no workaround for this issue.

  • Hot-Add fails with an File is larger than the maximum size supported by datastore error

    Backup operation of virtual machines in the hot-add fails with an File is larger than the maximum size supported by datastore `[<datastore_name>] error, when the backup virtual machine and the VCB-HELPER virtual machine are residing on datastores of different block sizes.This issue occurs when the .vmdk files of the backup virtual machine are greater than the maximum file size supported on the datastore of VCB-HELPER virtual machines.

    To work around this issue, VCB-HELPER virtual machines and the backup virtual machine should be residing on datastores of the same block size.

  • VCB cannot access the mounted files of Windows Server 2008 virtual machines having striped disks

    On Windows Server 2008 virtual machines, create and partition striped disks. Mount the Windows Server 2008 virtual machine using the vcbMounter command. Mounting is successful, but VCB cannot access the mounted files of Windows Server 2008 virtual machines having striped disks.

    Currently, there is no workaround for this issue.

  • Cannot create a virtual machine in the FT Mode when the virtual machine is backed up by VCB

    Because VCB operates on snapshots of virtual machines and Fault Tolerance (FT) does not work for virtual machines with snapshots, you cannot create a virtual machine in the FT mode while being backed up by VCB. FT disables snapshot operations for its virtual machines.

  • Hot-Add fails with an Failed to allocate SCSI target ID error

    VCB allocates SCSI target IDs to virtual disks from the backup virtual machine that will be added while the virtual machine is running (or "hot" added). If all target IDs in the proxy virtual machine are in use, the mount operation fails with the following error: Failed to allocate SCSI target ID. VCB cannot add a SCSI controller while the machine is running, so you must power off the proxy virtual machine to add SCSI controllers. The proxy virtual machine can be configured with up to four SCSI controllers.

    To add more than four SCSI controllers, add a virtual disk and use the vSphere Client to assign a target on a new SCSI controller.

  • VCB fails to find or mount virtual machines whose names contain the & character

    If a virtual machine's name contains an & character, VCB fails to locate and mount the virtual machine.

    To work around this issue, when running VCB commands that involve virtual machine's name containing & character, specify the virtual machine's name in double quotes.

    Example: vcbVMname -h <host-name> -u <username> -p <password> -s name:"<Vmname with & >"

  • Backup operation of virtual machines fails to mount after uninstalling and installing VCB 1.5 Update 1 on VCB Proxy (Windows Server 2008)

    After uninstalling and installing VCB 1.5 Update 1 on VCB Proxy (Windows Server 2008), file-level virtual machine backups fail with the following error: Cannot mount volume 1, Cannot open virtual storage driver. Make sure it is running. However, full virtual machine backup works correctly.

    To work around this issue, reboot the VCB Proxy and run the backup operation again.

  • 64-bit PowerPath installed on VCB Proxy is not supported

    Backup fails with an A virtual disk could not be opened. – Cannot open disk file: Error : Disk library failed error. This issue occurs if 64-bit PowerPath is installed on 64-bit VCB Proxy operating systems. For more information, refer Support for VMware Consolidated Backup (VCB) and Multipath software (KB 1007479).

  • vCenter Server displays an error during hot-add backups

    Occasionally, while using the hot-add backup, users might see the following message in the Recent Tasks panel of vCenter Server: The operation is not allowed in the current state. This message can be ignored as the backup operation continues.

  • Running custom quiescing scripts inside Windows guest operating system virtual machine with ESX 3.5 Update 2 and later (KB 1006671) †
  • Consolidated Backup and storage VMotion are mutually exclusive

    Because Consolidated Backup operates on snapshots of virtual machines and Storage VMotion does not work for virtual machines with snapshots, you cannot migrate a virtual machine while it is being backed up by Consolidated Backup. Storage VMotion, on its part, disables snapshot operations for virtual machines that it migrates.

    As a result, an attempt to back up such a virtual machine with Consolidated Backup fails with a resource in use error.

  • VSS not installed by default on Windows Server 2003 during VMware Tools upgrade on ESX 3.5 Update 2

    ESX 3.5 Update 2 introduces quiescing support using Volume Shadow Copy Service (VSS). However, VSS components are not installed when upgrading VMware Tools on a Windows Server 2003 virtual machine. You can install VSS components manually by performing an interactive tools upgrade with the VI Client:

    1. In the VMware Tools installer, select Modify > Drivers > VSS.
    2. Complete the installation process.
    3. Restart the virtual machine to make sure VSS components are installed and running.
  • VSS not installed by default on Vista and Windows Server 2008

    ESX 3.5 Update 2 introduces quiescing support using VSS. However, VSS components are not installed by default on Windows Vista and Windows Server 2008 virtual machines. You can install VSS components manually by performing an interactive tools upgrade with the VI Client:

    1. On the drive where the VMware Tools CD is mounted, locate the redist folder.
    2. Install vcredist_x86.exe (or vcredist_x64.exe on a 64-bit operating system).
    3. In the VMware Tools installer, select Modify > Drivers > VSS.
    4. Complete the installation process.
    5. Restart the virtual machine to make sure VSS components are installed and running.
  • Hot-Add fails with could not locate device nodes for new disks error

    Some applications install a virtual adapter in the guest operating system. These virtual adapters might interfere with the ability of Consolidated Backup to detect a disk that has been added while the machine is running to the proxy virtual machine when performing a mount operation.

    If the error Could not locate device nodes for new disks occurs during a hot-add mount operation, check the Windows device manager to see if any SCSI controllers other than those for LSI Logic or Buslogic are installed.

  • Hot-Add fails with Failed to allocate SCSI target ID error

    Consolidated Backup allocates SCSI target IDs to disks from the backup virtual machine that will be added while the machine is running (or "hot" added). If all target IDs in the proxy virtual machine are in use, the mount operation fails with the following error: Failed to allocate SCSI target ID. Consolidated Backup cannot add a SCSI controller while the machine is running, so you must power off the proxy virtual machine to add SCSI controllers.

    The proxy virtual machine can be configured with up to four SCSI controllers. To add more than four SCSI controllers, add a disk and use the VI Client to assign a target on a new SCSI controller.

  • Proxy virtual machine used with hot-add transport mode fails to power on

    During a hot-add mount operation, Consolidated Backup attaches the snapshot disks of the backup virtual machine to the proxy virtual machine. During a hot-add unmount operation, Consolidated Backup removes the snapshot disks of the backup virtual machine from the proxy virtual machine. If the unmount operation is performed manually (for example, a snapshot of the backup virtual machine is manually deleted) the operation might invalidate the disks that are still attached to the proxy virtual machine. As a result, the proxy virtual machine fails to power on.

    You must use the VI Client to reconfigure the proxy virtual machine manually, removing any disks attached to the virtual machine that did not originally belong to it. After such offending disks are removed, you can power on the machine. You can avoid this situation by using Consolidated Backup for the unmount operation on proxy virtual machines.

  • Backup fails with cannot use hot-add transport to mount virtual machines with independent disks error

    When you use hot-add transport to back up a virtual machine with an independent disk (including physical compatibility RDMs), the backup fails with the following error: Cannot use hotadd transport to mount virtual machines with independent disks.

  • File-level backups fail if .vmdk is expanded using vmkfstools -X

    If you use vmkfstools -X on an ESX 3.5 service console to expand the size of a virtual machine's disk, Consolidated Backup cannot run a file-level backup on the virtual machine, and can only run a fullvm backup. Attempts to run a file-level backup fail with the error message: "unable to open disk." This issue occurs because cylinder values are not updated by vmkfstools, and Consolidated Backup is unable to determine the size of the disk.

    To work around this issue:

    • (Preferred) Use the VI Client wizard, rather than vmkfstools, to expand the size of the virtual machine's disk, which will not change the cylinder's value.
    • If you have already used the vmkfstools -X option, you can manually modify the cylinder's value (use this method with caution):
      1. Navigate to /vmfs/volumes/storage/<vm-name>
      2. Open the vm-name.vmdk file for edit.

        The file contains lines similar to the following:
        RW 8388608 VMFS "vm-name-flat.vmdk"
        ddb.geometry.cylinders = "261"
        ddb.geometry.heads = "255"
        ddb.geometry.sectors = "63"

      3. Change the number of cylinders accordingly.

      For example, if the size of the .vmdk file was 4GB before you applied the vmkfstools -X option (RW 4194304 ...), and the new .vmdk size is 8GB (RW 8388608...), the number of cylinders should be doubled from 261 to 522.

      Before:
      RW 4194304 VMFS "vm-name-flat.vmdk"
      ddb.geometry.cylinders = "261"

      After:
      RW 8388608 VMFS "vm-name-flat.vmdk"
      ddb.geometry.cylinders = "522"

  • Windows pre-freeze.bat and post-thaw.bat scripts not invoked when upgrading from VMware Tools on ESX 3.5 to ESX 3.5 Update 2 and later

    When you update an ESX host and its guest virtual machine's VMware Tools to ESX 3.5 Update 2, the scripts in C:\Program Files\VMware\VMware Tools\backupScripts.d are invoked with a freeze or thaw argument during quiescing. However, the scripts C:\windows\pre-freeze.bat and C:\windows\post-thaw.bat are no longer invoked.

    To work around this issue, copy the scripts (pre-freeze.bat and post-thaw.bat) to the new script format as required by VMware Tools for ESX 3.5 Update 2. Refer the Virtual Machine Backup Guide for more information.

  • SCSI Controller order varies after importing a virtual machine with pvSCSI and LSI Controller

    Virtual machines imported to ESX Server fail to boot when powered on. This issue occurs when the guest operating system is installed on a SCSI virtual disk attached to VMware Paravirtual SCSI (pvSCSI) controller and another SCSI virtual disk is attached to the LSI Controller.

    To work around this issue, manually select the first bootable SCSI virtual disk attached to the pvSCSI controller in the BIOS of the virtual machine.

  • VCB Fails to create snapshot

    While mounting a backup virtual machine, the snapshot creation process might fail with the error Error: Other error encountered: Snapshot creation failed:Could not quiesce file system. vCenter Server reports the same error as Creating a quiesced snapshot failed because the created snapshot operation exceeded the time limit for holding off I/O in the frozen virtual machine.

    To work around this issue, use any of the following options:

    • If snapshots are taken with VSS quiescence, disable VSS tools in the virtual machine. This enables the SYNC driver to quiesce the virtual machine.

      Note: This workaround requires that the virtual machines be restarted.

    • Uninstall and install VMware Tools.

      Note: This workaround requires that the virtual machines be restarted.

    • Disable quiescing by appending -Q 0 to the vcbMounter command, or adding Quiesce = 0 for pre-backup jobs. Refer the Virtual Machine Backup Guide for more information.

      Note: -Q 0 refers to disabling the quiescing option.

Top of Page