o Makes the VM snapshot available to the third-party software.
o The backup software performs an ordinary backup of the VM snapshot moving the data to a backup medium.
o The backup software calls the post-backup script:
o Unmounts the VM snapshot from the backup proxy.
o Takes the VM out of snapshot mode.
o Types of VCB backups:
o Image-level backup
o File-level backup
o Full file backup
o Differential backup
o Incremental backup
o VCB proxy:
o Windows 2003 SP1 220 702 (32-bit or 64-bit)
o Windows 2003 R2 (32-bit or 64-bit)
o Windows 2003 SP2 (32-bit or 64-bit)
o Windows 2008 - Server Core (command line) not supported.
o Disable automatic drive-letter assignment to newly seen volumes:
o diskpart
o automount disable
o Clean out entries of previously mounted volumes: automount scrub
o VCB configuration file: C:\Program Files\VMware\VMware Consolidated Backup Framework\config\config.js
o You need to specify a user name.
o Use the same password you use for logging in to the vCenter host or ESX Server host.
o If you do not specify the password, VCB checks if the password is set in the registry.
o You can configure VCB to use Security Support Provider Interface (SSPI) for authentication.
o When VCB communicates with the vCenter server or ESX Server host, it can transfer data over an encrypted SSL connection or use an
unencrypted network channel.
o VCB supports a maximum of 60 concurrently mounted VMs disks.
o In the Hot-Add mode, you need to create a shadow VM for VCB to use internally. The shadow VM has the same name as your virtual VCB
proxy with the (VCB-HELPER) suffix added.
o If you are using VCB in the Hot-Add mode, in 9L0-403 addition to the VCB User role, you need to create the VMware VCB Proxy role.
o You cannot perform a file-level backup simultaneously with an image-level backup for the same VM.
o When you perform a first backup for a VM, the VM has to be powered on, otherwise the backup fails.
o You do not need to power on a VM if your integration module is configured to use VM display names instead of IP addresses or DNS names.
o VMware VSS Component. Guest operating systems:
o Windows Server 2003 32-bit/64-bit
o Windows Vista 32-bit/64-bit
o Windows Server 2008 32-bit/64-bit
o VCB uses the VMware VSS component to create quiesced snapshots of the VM volumes.
o 2003 - VSS snapshots are application-consistent.
o Vista & Windows Server 2008, the snapshots are file-system consistent.
o SYNC Driver
o XP 32-bit
o 2000 Server 32-bit
o 2003 32-bit
o SYNC driver holds incoming I/O & flushes all dirty data to a disk, making snapshots file-system consistent.
o Locations of Custom Quiescing Scripts:
o Pre-freeze - C:\Program Files\VMware\VMware Tools\backupScripts.d or /usr/sbin/pre-freeze-script - All scripts are invoked in ascending
alphabetical order with freeze as the first argument.
o Post-thaw - C:\Program Files\VMware\VMware Tools\backupScripts.d or /usr/sbin/post-thaw-script - All scripts are invoked in
descending alphabetical order with thaw or freezeFail as the first argument.
o Cleaning Up After a Failed Backup Job: 9L0-510 run vcbCleanup at the end of your backup cycle.
Appendix A: Using Service Console to Back Up & Restore VMs (valid for ESX4?)
o /etc/vmware/backuptools.conf configuration file to set the most common parameters
o You can use vcbMounter to back up an entire VM in the service console. The vcbMounter utility creates a quiesced snapshot of the VM &
exports the snapshot into a set of files, which can be later used to restore the VM.
o To search for a particular VM & get information about it, use vcbVmName.
o You can back up a VM to a local directory or to a remote server using scp.
o Use vcbSnapAll to create an archive of groups of VMs in the service console. The vcbSnapAll utility has the same functionality as vcbMounter,
but, in addition, can identify groups of VMs.
