How VMware Consolidated Backup Works
Consolidated Backup consists of a set of utilities and scripts that work in conjunction with a third-party backup software. To ensure that Consolidated Backup works with the specific backup software, either VMware or your backup software vendor provide integration modules containing any required pre-backup and post-backup scripts.
The third-party software, integration module, and Consolidated Backup run on the VCB proxy, a physical or virtual machine that has Microsoft Windows operating system installed.
For specific versions of Microsoft Windows, see Configuring Windows on the VCB Proxy.
VMware Consolidated Backup Usage Models
To store and manage virtual disk files, ESX Server uses a variety of physical storage devices, including local disks, NAS storage, Fibre Channel SANs, or iSCSI SANs.
For more information on different types of storage, see ESX Server 3 Configuration Guide or ESX Server 3i Configuration Guide.
The type of storage device your ESX Server system has access to determines how you set up the VCB proxy and the transportation method Consolidated Backup uses to access virtual disk data.
Consolidated Backup provides the following methods of accessing virtual machine disk data:
• SAN Mode – Use with Fibre Channel and iSCSI storage to completely off-load backups to a physical VCB proxy.
• Hot-Add Mode – Use with any type of storage to perform backups by a VCB proxy set up in a virtual machine.
• LAN Mode (NBD Mode) – Use when your environment does not permit the use of the SAN or Hot-Add modes.
SAN Mode
You select this mode when your ESX Server stores its virtual machine disks on Fibre Channel SAN or iSCSI SAN. When using this mode, you can completely off-load backups to a physical VCB proxy.
In addition with Fibre Channel, you avoid moving data across the network. In this case, if the VCB proxy is your media server, you can get completely LAN-free backups of your virtual machines.
SCSI Hot-Add Mode
In the SCSI Hot-Add mode, you set up one of your virtual machines as a VCB proxy and use it to back up other virtual machines residing on storage visible to the ESX Server that hosts the VCB proxy virtual machine. This mode eliminates the need of having a dedicated physical machine for your VCB proxy and does not require you to expose SAN LUNs to the Windows VCB proxy.
In this mode, you can use Consolidated Backup to protect any virtual disks on any type of storage available to your ESX Server host, including NAS or local storage. The only exception are physical compatibility RDMs.
Consolidated Backup creates a snapshot of the virtual disk to be protected and hot adds the snapshot to the VCB proxy, allowing it to access virtual machine disk data. The VCB proxy reads the data through the I/O stack of the ESX host.
To be able to run Consolidated Backup in the SCSI Hot-Add mode:
• You need to have ESX Server 3.5 or ESX Server 3i version 3.5 or later.
• If you are using only the local storage devices, you need a VCB proxy virtual machine on each ESX Server host.
• If you are using VirtualCenter, make sure to have version 2.5 or later installed.
Running Consolidated Backup in the SCSI Hot-Add mode provides the LAN-free capabilities of the SAN mode because the virtual disk data is transferred from the ESX Server I/O stack. Although this mode is not as efficient as the SAN mode, which does not cause any overhead on the ESX Server host, it is still more efficient than the LAN mode.
In this mode, Consolidated Backup uses an over-the-network protocol to access the virtual disk. The ESX Server host reads the data from the storage device and sends it across a network channel to the VCB proxy.
To be able to run Consolidated Backup in the LAN mode:
• You need to have ESX Server 3.5 or ESX Server 3i version 3.5 or later.
• If you are using VirtualCenter, make sure to have version 2.5 or later installed.
• Your virtual disks cannot be larger than 1TB each.
See here for VMware Consolidated Backup WorkFlow.
One of the advantages of purchasing VMware Infrastructure Enterprise (VI 3.5) is that along with the flagship ESX hypervisor there are additional licensed features and products included that are necessary to create business continuity for virtual machines (VMs). VMware Consolidated Backup (VCB) is one of these products. Often misunderstood as the complete answer for a virtual data center, VCB requires some preparation and understanding for backup administrators currently used to the traditional physical enterprise backup solution.
1. VCB is not the entire backup solution for virtual infrastructure:
It is very rare that VCB allows administrators to completely remove all backup agents from virtualized servers. This is because VMware Consolidated Backup does not:
Perform specialized application backups (like Microsoft Exchange Information Store or Windows Server System State)
Perform file-level backups of non-Windows VMs
Provide management, cataloging or archiving of backup files
Provide direct file restores to virtual machines
VCB is a framework of scripts that needs to be integrated with a third-party backup application to provide these features.
2. VCB should be installed on a dedicated Windows Server
It is recommended VCB be installed on its own server. Also known as the VCB Proxy Server, this system has the following requirements:
Microsoft Windows Server 2003 Service Pack 1 (32‐bit or 64‐bit) or higher
Media repository managed by the third-party backup application's management server
The same storage protocol access as the ESX hosts to the VMFS LUNs where the VMs are stored. (i.e., host bus adapters (HBAs) for access to Fibre Channel storage or initiator configuration for iSCSI storage). Depending on the version of Windows Server used, automatic partition mounting will have to be disabled before attaching the VCB server to the VMFS LUNs
Dedicated disk storage for the VCB Holding Tank where backup and restore files are written
Third-party backup agent
3. VCB needs a large disk volume for a Holding Tank
Along with the shared access to the ESX LUNs, VCB also needs a large disk volume formatted as NTFS, which will become the Holding Tank for backup images. This volume can be on the SAN or the local VCB server's disks. The Holding Tank volume is where full VM images are placed both during backups and restores.
Therefore, the size of the Holding Tank is critical in the design. For example, if a virtual infrastructure consists of VMs that take up 1 TB of disk space and the expectation is that a full VM backup is to be taken nightly, then the Holding Tank volume needs to be large enough to support 1 TB of backups. Another scenario would be to alternate groups of full VM backups in order to decrease the required size of the volume. In this case, administrators still need to make sure the Holding Tank is large enough to hold the VM using the most disk space.
4. The role of the third-party backup agent
The third-party backup application does the actual backing up and management of the files. Once VCB copies a VM image to the Holding Tank it is then up to the third-party backup application to move those files to whatever media repository is in use. It is also the function of the agent to clear out the Holding Tank so that the next scheduled job has available disk space to complete.
In the case of file-level backups, VCB also mounts the copied VM image (in thumb drive style as previously mentioned) so that the backup agent can see the VM's file system. The backup agent can then perform full, incremental or differential file-level backups to the media repository. In some scenarios, the single agent on the VCB server can replace the multiple agents on the VMs.
VMware maintains a compatibility guide for supported third-party backup applications. Many of these supported applications have VCB integration modules that coordinate the scheduling of the VCB scripts and the agent backup from within the application's GUI.
5. Understanding VCB restore jobs
Restoring files leverages the third-party backup agent's ability to move files from the media repository back to the Holding Tank. Once the VM image is back, it can be copied in full to a VMFS volume or mounted like a thumb drive again so that individual files can be restored. An administrator must manually copy files to the restore location in both scenarios.
VMware Converter, most often used to migrate physical servers to virtual machines, can also create VMs from VCB images. Therefore, VMware Converter can be a more effective full VM restore tool in some cases. Check out VMware's Virtual Machine Backup Guide for more detailed information on implementing VCB.
About this author: Rich Brambley is a Senior Infrastructure Consultant/Engineer working for Optimus Solutions in Norcross, GA. He specializes in virtual infrastructure, and has been designing and implementing various virtualization technologies for the last five years. Prior to becoming a consultant, he held various Operations Engineer positions and was responsible for the daily administration of Wintel applications and services. He has more than 10 years experience in IT. His VM/ETC blog is dedicated to everything related to virtualization.
Consolidated Backup consists of a set of utilities and scripts that work in conjunction with a third-party backup software. To ensure that Consolidated Backup works with the specific backup software, either VMware or your backup software vendor provide integration modules containing any required pre-backup and post-backup scripts.
The third-party software, integration module, and Consolidated Backup run on the VCB proxy, a physical or virtual machine that has Microsoft Windows operating system installed.
For specific versions of Microsoft Windows, see Configuring Windows on the VCB Proxy.
VMware Consolidated Backup Usage Models
To store and manage virtual disk files, ESX Server uses a variety of physical storage devices, including local disks, NAS storage, Fibre Channel SANs, or iSCSI SANs.
For more information on different types of storage, see ESX Server 3 Configuration Guide or ESX Server 3i Configuration Guide.
The type of storage device your ESX Server system has access to determines how you set up the VCB proxy and the transportation method Consolidated Backup uses to access virtual disk data.
Consolidated Backup provides the following methods of accessing virtual machine disk data:
• SAN Mode – Use with Fibre Channel and iSCSI storage to completely off-load backups to a physical VCB proxy.
• Hot-Add Mode – Use with any type of storage to perform backups by a VCB proxy set up in a virtual machine.
• LAN Mode (NBD Mode) – Use when your environment does not permit the use of the SAN or Hot-Add modes.
SAN Mode
You select this mode when your ESX Server stores its virtual machine disks on Fibre Channel SAN or iSCSI SAN. When using this mode, you can completely off-load backups to a physical VCB proxy.
In addition with Fibre Channel, you avoid moving data across the network. In this case, if the VCB proxy is your media server, you can get completely LAN-free backups of your virtual machines.
SCSI Hot-Add Mode
In the SCSI Hot-Add mode, you set up one of your virtual machines as a VCB proxy and use it to back up other virtual machines residing on storage visible to the ESX Server that hosts the VCB proxy virtual machine. This mode eliminates the need of having a dedicated physical machine for your VCB proxy and does not require you to expose SAN LUNs to the Windows VCB proxy.
In this mode, you can use Consolidated Backup to protect any virtual disks on any type of storage available to your ESX Server host, including NAS or local storage. The only exception are physical compatibility RDMs.
Consolidated Backup creates a snapshot of the virtual disk to be protected and hot adds the snapshot to the VCB proxy, allowing it to access virtual machine disk data. The VCB proxy reads the data through the I/O stack of the ESX host.
To be able to run Consolidated Backup in the SCSI Hot-Add mode:
• You need to have ESX Server 3.5 or ESX Server 3i version 3.5 or later.
• If you are using only the local storage devices, you need a VCB proxy virtual machine on each ESX Server host.
• If you are using VirtualCenter, make sure to have version 2.5 or later installed.
Running Consolidated Backup in the SCSI Hot-Add mode provides the LAN-free capabilities of the SAN mode because the virtual disk data is transferred from the ESX Server I/O stack. Although this mode is not as efficient as the SAN mode, which does not cause any overhead on the ESX Server host, it is still more efficient than the LAN mode.
LAN Mode (NBD Mode)
You select this mode when your ESX Server does not have access to a SAN, but uses local storage devices or NAS to store its virtual machine disks.In this mode, Consolidated Backup uses an over-the-network protocol to access the virtual disk. The ESX Server host reads the data from the storage device and sends it across a network channel to the VCB proxy.
To be able to run Consolidated Backup in the LAN mode:
• You need to have ESX Server 3.5 or ESX Server 3i version 3.5 or later.
• If you are using VirtualCenter, make sure to have version 2.5 or later installed.
• Your virtual disks cannot be larger than 1TB each.
See here for VMware Consolidated Backup WorkFlow.
One of the advantages of purchasing VMware Infrastructure Enterprise (VI 3.5) is that along with the flagship ESX hypervisor there are additional licensed features and products included that are necessary to create business continuity for virtual machines (VMs). VMware Consolidated Backup (VCB) is one of these products. Often misunderstood as the complete answer for a virtual data center, VCB requires some preparation and understanding for backup administrators currently used to the traditional physical enterprise backup solution.
1. VCB is not the entire backup solution for virtual infrastructure:
It is very rare that VCB allows administrators to completely remove all backup agents from virtualized servers. This is because VMware Consolidated Backup does not:
Perform specialized application backups (like Microsoft Exchange Information Store or Windows Server System State)
Perform file-level backups of non-Windows VMs
Provide management, cataloging or archiving of backup files
Provide direct file restores to virtual machines
VCB is a framework of scripts that needs to be integrated with a third-party backup application to provide these features.
2. VCB should be installed on a dedicated Windows Server
It is recommended VCB be installed on its own server. Also known as the VCB Proxy Server, this system has the following requirements:
Microsoft Windows Server 2003 Service Pack 1 (32‐bit or 64‐bit) or higher
Media repository managed by the third-party backup application's management server
The same storage protocol access as the ESX hosts to the VMFS LUNs where the VMs are stored. (i.e., host bus adapters (HBAs) for access to Fibre Channel storage or initiator configuration for iSCSI storage). Depending on the version of Windows Server used, automatic partition mounting will have to be disabled before attaching the VCB server to the VMFS LUNs
Dedicated disk storage for the VCB Holding Tank where backup and restore files are written
Third-party backup agent
3. VCB needs a large disk volume for a Holding Tank
Along with the shared access to the ESX LUNs, VCB also needs a large disk volume formatted as NTFS, which will become the Holding Tank for backup images. This volume can be on the SAN or the local VCB server's disks. The Holding Tank volume is where full VM images are placed both during backups and restores.
Therefore, the size of the Holding Tank is critical in the design. For example, if a virtual infrastructure consists of VMs that take up 1 TB of disk space and the expectation is that a full VM backup is to be taken nightly, then the Holding Tank volume needs to be large enough to support 1 TB of backups. Another scenario would be to alternate groups of full VM backups in order to decrease the required size of the volume. In this case, administrators still need to make sure the Holding Tank is large enough to hold the VM using the most disk space.
4. The role of the third-party backup agent
The third-party backup application does the actual backing up and management of the files. Once VCB copies a VM image to the Holding Tank it is then up to the third-party backup application to move those files to whatever media repository is in use. It is also the function of the agent to clear out the Holding Tank so that the next scheduled job has available disk space to complete.
In the case of file-level backups, VCB also mounts the copied VM image (in thumb drive style as previously mentioned) so that the backup agent can see the VM's file system. The backup agent can then perform full, incremental or differential file-level backups to the media repository. In some scenarios, the single agent on the VCB server can replace the multiple agents on the VMs.
VMware maintains a compatibility guide for supported third-party backup applications. Many of these supported applications have VCB integration modules that coordinate the scheduling of the VCB scripts and the agent backup from within the application's GUI.
5. Understanding VCB restore jobs
Restoring files leverages the third-party backup agent's ability to move files from the media repository back to the Holding Tank. Once the VM image is back, it can be copied in full to a VMFS volume or mounted like a thumb drive again so that individual files can be restored. An administrator must manually copy files to the restore location in both scenarios.
VMware Converter, most often used to migrate physical servers to virtual machines, can also create VMs from VCB images. Therefore, VMware Converter can be a more effective full VM restore tool in some cases. Check out VMware's Virtual Machine Backup Guide for more detailed information on implementing VCB.
About this author: Rich Brambley is a Senior Infrastructure Consultant/Engineer working for Optimus Solutions in Norcross, GA. He specializes in virtual infrastructure, and has been designing and implementing various virtualization technologies for the last five years. Prior to becoming a consultant, he held various Operations Engineer positions and was responsible for the daily administration of Wintel applications and services. He has more than 10 years experience in IT. His VM/ETC blog is dedicated to everything related to virtualization.
![HP Data Protector - [61:12500] cannot connect to inet for getting file system list on host](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgspn5NG8tEmjj5Xzbc0tmr2kIxxoQtKH3SvCGZFUWR7Sa7Q_hjKEMXJHSsw8T6ILflqVpQ68OrtdMn48o5feFi3b50lM3QNKJIYHVjqZ_ReWhIOTrFC_Rwc5FX2HZkr77DlKqbLK_2Kk4/s72-c/HP-Data_protector-backup-tool.png "HP Data Protector - [61:12500] cannot connect to inet for getting file system list on host")
What a data of un-ambiguity and preserveness of valuable familiarity regarding unexpected emotions.
ReplyDelete