What's in the Release NotesThe release notes cover the following topics:
This release of VMware Consolidated Backup (VCB) version 1.1 Update 1 offers the following improvements:
Features and known issues from VCB 1.0.3 Update 1 and VCB 1.1 are described in the release notes for each release.
Upgrading from VMware Consolidated Backup 1.1 Update 1 to later versions of VMware Consolidated Backup
To upgrade to the later versions of VCB, uninstall the VMware Virtual volume storage bus drivers from Windows operating systems, run the VMware-vcb-xxxxx.exe (where xxxxx is a build number), and follow the on-screen instructions to complete the upgrade. To determine the version and build number of VCB, refer the Determining VCB versions and build numbers KB.
VCB1.1 Update 1 requires the following versions of ESX Server and VirtualCenter:
When using the SNAPSHOT_POLICY option in the config.js file as "deleteonly" or "manual," VCB incorrectly deletes the snapshot when the pre-command script is called with the PREEXISTING_VCB_SNAPSHOT option set to "delete." The workaround is to set PREEXISTING_VCB_SNAPSHOT="fail" in the config.js file.
For this release, a number of critical issues have been fixed, improving general performance, reliability, and robustness of VCB.
This fix resolves an issue where the backed up virtual machine files mounted on VCB proxy server are not accessible after a HA failover operation. Additionally, this fix eliminated renew disk lease issue, which resulted in a disk lease time out Consolidated Backup error message.pre-command Script Fails When Transport Mode is Set to nbdssl in config.js
When the transport mode in config.js file is set to nbdssl, the pre-command script fails with the Illegal value for config option TRANSPORT_MODE: nbdssl error message. The issue is fixed in this release.Consolidate Helper Snapshots Might Not Be Removed Automatically
Starting from ESX Server 3.5 Update 2 release, Consolidate Helper snapshots are created iteratively to minimize the amount of time a virtual machine is inactive during snapshot creation. As a result, the Consolidate Helper snapshots are now called Consolidate Helper-XXX and not just Consolidate Helper.
When you use VCB 1.1 with ESX Server 3.5 Update 2, if vcbMounter command encounters a failure during a snapshot delete operation, the temporary snapshots might be left behind on the ESX Server host. Even the vcbCleanup.bat command does not delete this Consolidate Helper-XXX snapshot. You must manually delete it using VI Client. This issue does not exist in VCB 1.1 Update 1.Upgrades from VCB 1.0.x to VCB 1.1 Fail
VCB 1.0.x does not upgrade to VCB 1.1, causing VCB 1.0.x to stop responding. This issue occurs due to the virtual storage driver not getting upgraded. VCB 1.1 Update 1 can be upgraded to higher versions of VCB. The issue is fixed in this release.vcbMounter Command Fails to Create Mount Directory
vcbMounter command fails to create a mount directory if the directory does not exist. The issue is fixed in this release.VCB Generates Error If Password Is Not Located
Specifying passwords as command-line arguments is nonsecure. Starting with this release, VCB offers a secure way for handling passwords.
When the pre-backup.bat script runs for a non-existent virtual machine, code 0 is returned instead of code 16. The issue is fixed in this release.vcbVmName Command on Non-ASCII Windows Consolidated Backup Proxy Server Displays Garbled Characters
Running the vcbVmName command on a non-ASCII Windows Consolidated Backup proxy servers like Japanese, Russian, Chinese, etc, displays the non-ASCII name of the virtual machine as garbled characters. This issue is fixed in this release.SNAPSHOT_POLICY Option Set as createonly Does Not Work
When SNAPSHOT_POLICY option is set as createonly in the config.js file, VCB incorrectly deletes the snapshot when the post commands are run. The issue is fixed in this release.VCB Script Layer Fails to Remove Snapshot
The VCB script layer fails to remove a snapshot for virtual machine whose name contains spaces. The issue is fixed in this release.pre-backup.bat Script Fails with Incorrect Error Message When Wrong Password Is Specified
When a wrong password is specified in the config.js file, running the pre-backup.bat script generates an incorrect error message, which cites the reason as an unknown virtual machine and the wrong exit code 16. The correct error message is Check hostname,username and password Exit Code: 18 checking for virtual machine. The issue is fixed in this release.