Automated Veeam Cloud Connect deployment 5: Replication services for vCloud Director

0 Flares Twitter 0 Facebook 0 LinkedIn 0 Email -- 0 Flares ×

In chapter 3 of this blog series, I showed you how to connect a vCloud Director to Veeam Backup & Replication. Before Veeam Backup & Replication 9.5 Update 4, the main usage of vCloud Director was to make backups of vCloud VMs. But now with Update 4, we can use vCloud Director as a target for Cloud Connect replicas.

Again, we first need the correct credentials. But now with vCloud Director Veeam Cloud Connect doesn’t use its local users, rather it maps tenants to existing vCloud Director organizations. In my lab this is the configuration I have so far:

The customer “vcc-tenant2” wants to consume Cloud Connect, so I first created for them a dedicated vDC named “DR”. You can use any vDC belonging to the organization as a target for Cloud Connect by the way, I just thought it would have been a good use case to have a tenant with both production VMs already running in vCloud Director, and also a new vDC to replicate VMs from another location.

Now, we need to give this customer access to Cloud Connect. The piece of code to do so is this:

Ok, the first 60 lines are a couple of nice functions I found that makes it easy to create a selection menu. The interesting part for us is at the end. After we connect to the Veeam Server, we list all the existing vCD organizations, we ask the operator which one he wants to enable in Cloud Connect, and we create thew new Cloud Connect tenant:

The tenant is created with no resources, but you can see that it’s of the type “vCloud Director”:

The next part of the script goes and enables replication:

There are two gateway pools (see this previous post about how to create them), and the script also shows me the two available vDCs. I choose the DR one, and the script enables the replication towards this one in Cloud Connect:

This is the code used for the second part of the script: