Chapter 24. VMware consolidated backup with Tivoli Storage Manager V5.5 335
the steps and then follow them in order, particularly if this is your first time using VCB or the
first VCB set up in your enterprise. Where steps are specified as optional, we recommend
that you do them anyway, particularly for a first installation, since they provide more
diagnostic steps than the minimum, and may help work out what is going wrong if problems
are encountered.
As a reminder, our environment, shown in Figure 24-3 on page 329, is:
򐂰 VMware ESX server: PEGASUS IP address
򐂰 VC server on Windows 2003: KCW09B, IP address
򐂰 VCB proxy node on Windows 2003: MENSA, IP address
If you wish to use LAN-free backup from the proxy node to the Tivoli Storage Manager
storage, you should install the Tivoli Storage Manager Storage Agent on the proxy and
configure it as a LAN-free client of the Tivoli Storage Manager server.
򐂰 VMware guests running Windows XP:
Host names are SPANIEL, MCNAB, MALAMUTE, and COLLIE, IP addresses to
VM names are ITSOVM1, ITSOVM2, ITSOVM3, ITSOVM4, respectively
򐂰 Tivoli Storage Manager V5.5 server, LOCHNESE, IP address
24.3.1 Prerequisites for VMware and operating system settings
In order to allow VCB to function, we have to configure a number of settings on our proxy
1. Prevent the Windows 2003 proxy node, MENSA, from assigning drive letters to new disks
automatically whenever it mounts disks from the ESX server on Windows via the SAN. We
use the Windows diskpart command for this, as shown in Example 24-1.
Example 24-1 Disable automatic disk drive letter assignment
C:\Documents and Settings\Administrator>diskpart
Microsoft DiskPart version 5.2.3790.3959
Copyright (C) 1999-2001 Microsoft Corporation.
On computer: MENSA
DISKPART> automount disable
Automatic mounting of new volumes disabled.
DISKPART> automount scrub
DiskPart successfully scrubbed the mount point settings in the system.
Automatic mounting of new volumes disabled.
Leaving DiskPart...
C:\Documents and Settings\Administrator>shutdown /r
2. Install VCB Framework on the proxy node.
VCB Framework is a component of the VMware Infrastructure 3 package, which can be
downloaded from:
Important: You must reboot Windows in order for the diskpart change to take effect.
This must be done before attempting to use or test VCB. The setting persists over
reboots. It only needs to be done once.
336 IBM Tivoli Storage Manager Versions 5.4 and 5.5 Technical Guide
A valid license is required. See your VMware administrator for licensing information.
Installing VCB Framework is straightforward. You are only prompted for the installation
directory. Figure 24-8 on page 336 shows a Windows dialog that asks whether you want to
install the VMware driver since it has not been through MS-WHQL testing. You must
accept and install this for VCB to work.
Figure 24-8 Driver installation dialog for VMware Consolidated Backup Framework
Note: At the time of writing, some VCB Framework versions available from VMware did
not automatically create the directory where the guest’s snapshotted file system will be
mounted. If you have a version with this issue, the backup operation will fail if the
directory does not exist, with the error:
007-11-28 14:28:59.265 'vcbMounter' 1960 error] Error: <directory-name>: Is
not a writeable directory.
A fix is expected to be available. Check for the availability of APAR IC54709. A
workaround for this is to manually create the mountpoint and make it read-only before
running the backup. This ensures that the mountpoint will persist. You can use
commands similar to:
mkdir c:\mnt\tsmvmbackup\filelevel
attrib +r c:\mnt\tsmvmbackup\filelevel
Chapter 24. VMware consolidated backup with Tivoli Storage Manager V5.5 337
Figure 24-9 on page 337 displays after the installation successfully completes.
Figure 24-9 VCB Framework installed
Once VCB Framework is installed, there is no further configuration required.; Tivoli
Storage Manager will automatically call VCB Framework with any required parameters.
3. Install VMware Tools on each virtual machine guest.
VMware Tools allows VMware to force a sync of the file systems before the snapshot
occurs, thus assuring file system integrity. The file system sync does not by itself ensure
that all files backed up in this manner will be consistent for the applications that use them
(for example, many applications such as databases will hold transactions in flight, which
will not be flushed using this sync). Rather, the sync ensures that the snapshot of the file
system itself is not rendered dirty or corrupted by the snapshot processing.
a. To check whether the VMware Tools are installed, look at the field VMware Tools for
each guest in the Virtual Infrastructure Client, as shown in Figure 24-10. If the field
displays not running, as here, you must install the VMWare tools.
Figure 24-10 VMware Tools not installed

Get IBM Tivoli Storage Manager Versions 5.4 and 5.5 Technical Guide now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.