6.6 vCloud replication jobs

Starting from Veeam Backup & Replication 9.5 Update 4, tenants can consume replication resources based on VMware Cloud Director, if their service provider offers it.

The first step into consuming Cloud Director resources is to connect as usual to the service provider and scan for the offered resources. The tenant needs to use a Cloud Director account, that is defined as Tenant\Org_Admin:

Login with a Cloud Director account type

6.44: Login with a Cloud Director account type

Using these credentials, the tenant connects to Cloud Connect and scans for the available resources:

Scan for new replication resources

6.45: Scan for new replication resources

The assigned vDC shows up in the Replica resouces, and once the setup wizard is completed, the remote vDC is also visible in the Backup Infrastructure:

vCloud Director cloud host

6.46: Cloud Director cloud host

Once the remote Cloud Director is registered, the replication jobs can be configured in the same way as the vSphere ones, using in particular the Network Mapping option to map local networks to the remote ones.

By default, a dedicated vApp names Cloud Connect is suggested and created:

Destination options in the replication job

6.47: Destination options in the replication job

Tenants can also specify different existing vApps as targets:

Select destination vApp

6.48: Select destination vApp

In the Network settings, tenants can map the local networks used by the replicated virtual machines to the remote one available in Cloud Director:

Available ORG networks

6.49: Available ORG networks

Network mapping in the replication job

6.50: Network mapping in the replication job

Once the job is saved and scheduled, VM’s are replicated to Veeam Cloud Connect, and the tenant can see them in the Cloud Director environment:

Virtual machines replicated to Cloud Director

6.51: Virtual machines replicated to Cloud Director

In the tenant environment, replicated virtual machines show up in Ready state in Veeam Backup & Replication, ready to be used for failover activities:

Virtual machine replicas in ready state

6.52: Virtual machine replicas in ready state