4.2 VMware vCloud Director
In addition to the ongoing support for VMware vSphere and Microsoft Hyper-V, Veeam Cloud Connect 9.5 Update 4 adds the support for native replication services towards VMware vCloud Director (8.10 and above).
In oder to consume vCloud Director replication, also the tenant must run Veeam Backup & Replication 9.5 Update 4.
Underlying vSphere environment
The vSphere comments exposed in the previous chapter are valid also for vCloud Director: from an infrastructure point of view, vCloud Director is on top of the vSphere environment, and the two layers can even be offered at the same time to Cloud Connect tenants.
The most important information, when consuming vCloud Director, is that in this case Veeam Cloud Connect DOES NOT CREATE ANY NEW OBJECT like in vSphere environments. No hardware plan, no portgroups, no vlans; Cloud Connect simply connects to vCloud Director and consumes existing resources already created there. So, any resource that needs to be exposed to a tenant has to be created in advance in vCloud Director.
This is a feature mapping chart between the two layers:
|Tenant||Local account||vCloud Organization|
|Resources||Hardware Plan (resource pool)||Org vDC (Virtual DataCenter)|
|Networking||VLAN-backed portgroups||VXLAN Org Networks|
|Router/Firewall||Veeam NEA||VMware NSX|
Veeam Backup & Replication needs to connect to both vCloud Director and the connected vSphere environments. During the setup of the vCloud Director environment in the Veeam console:
4.6: Add vCloud Director
a credential to connect and operate on vCloud Director is required. A dedicated account for Veeam Cloud Connect should be created in the vCloud environment with role System Administrator:
4.7: Add a new user in vCloud Director
With this dedicated account, it is easier to filter logs and identify activities belonging to Veeam Cloud Connect in vCloud Director, so that problem solving should be easier. Additionally, it is extremely easy to disable any access of Veeam Cloud Connect to the vCloud environment, if needed, by simply disabling this user.
Once the user is created the user can be configured in Veeam when registering vCloud Director:
4.8: Specify dedicated user account to connect to vCloud Director
One additional step compared to the registration of vSphere is the connection to the underlying vCenter servers. Plural because one vCloud Director system can manage multiple vCenter servers at the same time. These servers need to be specifically registered as belonging to vCloud Director even if they have been already registered as standalone vCenter servers before in Veeam Cloud Connect:
4.9: Register all the connected vCenter servers
The registration process is correctly completed, and vCcloud Director is added to the managed platform:
4.10: vCloud Director is added to Veeam Backup & Replication