VMware VCB To Be Replaced by VADP. Does That Mean vDR Is The VMware Alternative?
I received an email today from VMware addressed to all customers about the end of availability for VMware Consolidated Backup (VCB). Quoting from the beginning of the communication but not the entire message, it reads:
“The purpose of this letter is to inform you of our vSphere backup product strategy, ongoing enhancements, and end of availability plans for VMware Consolidated Backup.
VMware Backup Product Strategy
VMware released vStorage APIs for Data Protection (VADP) with the vSphere 4.0 release in May, 2009. VADP is the next generation of VMware’s backup framework. We have also been working with several backup partners to integrate VADP into their solutions to make backup of vSphere Virtual Machines fast, efficient and easy to deploy compared to VCB and other backup solutions. Several of our major backup partners have already released VADP integrated backup products and we expect most of the major backup partners to have VADP integrated backup software by the upcoming feature release of the vSphere platform in 2010.
Future Product Licensing
Given the strong interest and adoption of VADP by our backup eco-system and the benefits offered by VADP compared to VMware Consolidated Backup (VCB), we are announcing the End of Availability for VCB starting with next vSphere feature release in 2010. Starting with the next vSphere platform feature release, VCB will be removed from vSphere platform. VADP integrated backup products (including VMware Data Recovery) will be the recommended option for efficient backup and restoration of vSphere Virtual Machines. This will allow us to focus new value added feature development on VADP instead of two backup frameworks (VCB and VADP).”
I’ll go out on a limb and say that most of the VMware community will
help VCB “pack it’s bags” as quick as possible, but does that mean VMware’s vDR will be VCB’s replacement? If so VMware is going to have to expand the scalability of vDR’s current combination of virtual appliance and vSphere Client plugin, in my opinion.
The email doesn’t provide any hints about the future of vDR, but here are some thing to think about if you are considering vDR as VCB’s replacement:
(The following has been taken from http—www.vmware.com-pdf-vdr_11_admin.pdf)
- Virtual machines to be backed up and the backup appliance must both be running on ESX 4 or later or ESX 4i or later. Do not use Data Recovery with vCenter Servers running in linked mode.
- Recovery does not support:
- vCenter Server in Linked Mode.
- Pv6 addresses. IPv4 addresses are required for the Data Recovery appliance.
- NFS is only supported if the share is presented by an ESX Server and the VMDK is assigned to the Data Recovery appliance.
- Hot adding disks with versions of vSphere that are not licensed for hot add
- Restoring linked clones. Data Recover can backup linked clones, they are restored as unlinked clones.
- Backing up virtual machines that are protected by VMware Fault Tolerance.
- Backing up virtual machines that use VMware Workstation disk format.
- Backing up virtual machines with 3rd party multi-pathing enabled.
- Raw device mapped (RDM) disks in physical compatibility mode.
- Data Recovery has been tested for use with:
- One backup appliance for each vCenter instance.
- Each backup appliance protecting up to 100 virtual machines.
- VMDK or CIFS based deduplication stores of up to 1TB.
- Up to two deduplication stores per backup appliance.
In the immediate future it appears that third party VADP based products may be the best replacement for VCB, but I’ll be watching for future changes to VMware’s VDR as well.