I was planning on upgrading today until I re-read the release documents for all the associated components. So first of all, VCB is not going away immediately with version 4.1 of vSphere http://kb.vmware.com/kb/1026945... however, you can no longer restore full VM images with the utility. If you need to do so, you have to use VMware Converter, but wait! You can't use the latest version of Converter, you have to use a previous version http://kb.vmware.com/kb/1026944. Furthermore, if you are trying to back up VMs with Windows 2008/Windows 7 installed, this isn't supported under VCB 1.5 Update 2 and Converter 4.0.1 http://www.vmware.com/support/vsphere4/doc/vsp_vcb_15_u2_rel_notes.html#knownissues.
Am I reading this correctly? Aside from holding off on my upgrade to version 4.1, does any one have any constructive suggestions? I use VCB coupled with a VBS script to perform full VM backups once a month. This is a cheap-o method, but we primarily leverage third party backup agents (Microsoft Data Protection Manager) inside the VM guests.
Have you considered Data Recovery or Veeam Backup ?
If this post has been helpful/solved your issue, please mark the thread and award points as you see fit. Thanks!
This is a cheap-o method, but we primarily leverage third party backup agents (Microsoft Data Protection Manager) inside the VM guests.
If you already use 3rd party backup, why are you concerned with VCB? That's the product, not the API. If your 3rd party fully supports the VCB API, that's all you need to backup. Agents are not a good idea for VM's, but you aren't using VCB to begin with.
Or use VDR that's still "cheap-o". VDR doesn't use VCB AT ALL.
I've considered both Veeam's product and the new vDR solution that VMware provides. Both would incur additional licensing costs (we run vSphere Standard Edition), maybe not too much... but since the previous solution (VCB) was included in the package, I'm still weighing all (including free) options.
Also, to clarify a little about our backup strategy - we use VCB as a secondary means of backing up certain critical VMs. The backups are taken once a month, and just serve as a "second" option in situations where we either need to restore a full VM or in some cases deploy a clone for testing purposes (yes, I could clone the VM as well, which I do utilize in some cases). Our primary solution for system backups is Microsoft Data Protection Manager, which has never provided support for VCB integration.