You’ve deployed your Rubrik virtual appliance (technically I should have used Air but let’s just go with it) and now you want to protect a VMware Cloud Director instance. When you add an instance, Rubrik automatically discovers all of the components of your VCD environment, including:
- Organization virtual datacenters;
- vApps; and
- Virtual machines.
You can protect vApps by assigning the SLA Domain at various levels in the VCD hierarchy, and also by assigning it to individual VMs. vApp protection also protects vApp metadata including networks, boot order, and the access list. There are a few limitations with vApp protection to keep in mind as well.
|Virtual machines in a vApp||Maximum of 128 virtual machines in a vApp. To protect a vApp with more than 128 virtual machines, use the exclude function to reduce the number protected.|
|Mounts||The Rubrik cluster performs all mounts for vApps at the virtual machine level.|
|Backup exclusion||Protection of vApps does not include Cloud Director Object Metadata.|
|Autodiscovery||Rubrik CDM ignores the Cloud Director auto discovery feature.|
There’s good support for multi-tenancy and RBAC as well. There’s a bunch of other stuff I could write about VCD and Rubrik but let’s just get started on adding an instance. Click on the Gear and select “vCD Instances”.
Then click on “Add vCD Account”.
You’ll then have the opportunity to enter your credentials.
I use all dots for my password too.
Once you’ve added the instance you’ll see it listed under “All vCD Instances”.
If you look under “Virtual Machines” you should see any vApps associated with the instance listed under “vCD Apps”. In this example my tenancy only has one vApp deployed.
And that’s it. This all gets a lot more interesting when you start messing about with the Rubrik VCD plug-in and the API, but that’s a story for another time.