There is one thing that we all can agree on, vCloud Director is materially different from what we’ve done in vSphere by itself. With the rich capabilities of self-provisioning, virtual data centers, additional storage options and more; there is more than just getting a virtual machine stood up.
The vCloud Director constructs such as vApps, Fast Provisioning configuration, leases, security ownership and more are key areas that need protection. The underlying vSphere infrastructure is, in some regards, materially the same as it has been for years; as that is where a key set of APIs are available for data protection: the vSphere APIs for Data Protection or VADP. Aside from VADP, there are additional APIs and web services to interact with. The vCloud API is a new set of APIs that are clearly on top of the vSphere APIs; including VADP. The vCloud API provides interactions in the following categories:
- Exploring a Cloud
- Provisioning an Organization
- Deploying and Operating vApps
- Creating and Managing Organizations
- Managing and Monitoring a Cloud
These align critically to the actions in the vCloud Director Web interface and what may have been done from a provider or an organization in the vCloud Director environment. So, with all of that being said; what do I need to know about backups?
With Veeam Backup & Replication v7 (disclosure: Rick Vanover works for Veeam and this is a guest blog post), there is now enhanced support for vCloud Director backup and restore capabilities. It’s also important to note that you can even backup vCloud Director VMs (including the vCloud metadata) with Veeam Backup Free Edition.
Now with Veeam Backup & Replication v7; vCloud Director VMs can be backed up with full awareness of the vCloud API constructs. Communication to vSphere for the VADP APIs is also performed with really the same effect as doing backups with Veeam as you may have done them before. The figure below shows the vCloud metadata being saved for a backup job that backs up every vApp (and VM) within an Organization VDC from one vCloud Director Cell:
That’s the critical step, backing up the VM’s configuration within the vCloud Director construct. The vCloud API doesn’t provide a loose equivalent of VADP; so to protect the VM the platform (vSphere) still provides VADP to back up the VM. In this example, the backup job backs up everything in two different vCloud Director Organizations; including any VMs or vApps that are added. That’s important in a world of self-provisioning. The figure below shows where VAPD kicks in to back up the VM:
Now that’s really the easy part, the backup of the VM. Sure, there is awareness to capture the vCloud Director information such as owner, lease, fast provisioning configuration, etc. But when it comes to restoring this backup; companies need options.
The restore options of Veeam Backup & Replication support restores to different vCloud Director Cells, different vApp networks, different Fast Provisioning configurations and more. Of course, the VMs (and vApps) can be restored right back to where they came from. The figure below shows the restore wizard:
All of this is put together with Veeam’s advanced vSphere processing engine that provides built-in compression and – of the backups, the ability to write backups to any storage and to off-site locations; including cloud targets.
What is your biggest challenge with backups of vCloud Director VMs? Share your challenges below and let’s discuss.
BIO: Rick Vanover (vExpert, MCITP, VCP) is a product strategy specialist for Veeam Software based in Columbus, Ohio. Rick is a popular blogger, podcaster and active member of the virtualization community. Rick’s IT experience includes system administration and IT management; with virtualization being the central theme of his career recently. Follow Rick on Twitter @RickVanover or @Veeam.