It has been a whirlwind month for the Veeam Teeam coming off a great showing at VMworld 2010 in San Francisco. While Veeam was collecting more awards for the corporate mantle last week, there was some great knowledge exchange taking place by the Veeam technical team as well.
A good friend of ours, Michael White with VMware let me know about a blog post he had forthcoming following the public announcement of VMware's vCloud Director product general availability. Michael is the Americas Solution Specialist SE for business continuity and disaster recovery for VMware. He contributes to the Uptime (Business Continuity) Blog at vmware.com.
Michael has been doing a good deal of testing with vCloud Director specifically in his domain of expertise. In his latest blog post he describes some of his results. Specifically of interest to me is Michael's testing of Veeam Backup & Replication v4 and the native ability to protect VMs that have been provisioned by vCloud Director.
If you are using agent based backups already in your organization, you can continue to do that. This may not work for you depending on the security that you have enabled in your cloud. If you are using the vStorage API set for the backup it may or may not work for you. Currently, the VMware Data Recovery (vDR) product will not work when backing up vCD provisioned VM's. This should be fixed in the next release of vDR. But generally, your software should work. In my testing I used vDR v1.2 (which didn't work), Backup Exec 2010 R2 13.0 Rev 4164 (agent based and worked) and Veeam 18.104.22.168 (which worked).
So if you want to start testing the new vCloud family of products, know that Veeam Backup & Replication, which is built on a solid architecture using available APIs and best practices, has you covered both today and in future.
A big thank you goes to Michael White for the testing and acknowledgment.
GD Star Rating loading...
Veeam vPower and VMware vCloud Director, 5.0 out of 5 based on 2 ratings