How to Map Replicas in Cloud Connect

KB ID: 2158
Products: Veeam Cloud Connect
Version: 9.x
Last Modified: 2016-09-02


When creating a replication job, seeding or mapping can be used to minimize the amount of traffic sent to a Cloud Service Provider. In most cases, seeding is the preferred method because it is not possible to map a Cloud Connect replication job to a replica that was not created with Cloud Connect. However, it is possible for a Cloud Service Provider to work around this limitation by replicating the existing replica.

Note: it is not possible to use a backup of a replica as a seed, because Veeam searches the backup file for the ID of the VM to be replicated, which is different from the ID of the replica.


These steps must be performed by a Cloud Connect Service Provider. 
Tenants who are unable to map replicas should ask their service provider whether this workaround is available.

  1. Connect a console to a Veeam backup server with access to the infrastructure containing the original replica. Typically this will be a backup server with a per-socket license, and not the SP Veeam backup server used to provide cloud resources to tenants.
  2. Use the tenant’s credentials to connect to a cloud gateway.
  3. Create and run a job to replicate the original replica into the cloud infrastructure. When configuring the job, consider that adding the default suffix will result in VMs named *_replica_replca.
  4. Delete the replication job created in step 3; do not delete the replica.
  5. Remove the service provider that was configured in step 2. Advise the tenant to proceed with the steps below.
Note: The console used for these steps may still display the replica after the service provider is removed in step 5; the replica should not appear the next time the console is opened.

These steps must be performed by the tenant:
  1. In the Backup Infrastructure view, add or rescan the cloud service provider.
  2. Verify that the replica is visible in the Replicas node of the Backup & Replication view. Press F5 to refresh the view if needed.
  3. Map the replica to a replication job. This must be done manually; the Detect option is not available.
  4. Run the mapped job and test the replica. Let the service provider know that they may proceed with the final steps.
These steps must be performed by a Cloud Connect Service Provider:
  1. Both SP and tenant will see duplicate replicas (with different source VMs) in the console. To resolve this, the SP must remove the older replica from configuration.
  2. (Optional) When the new replica has been tested successfully, the Service Provider may delete the original replica that is no longer needed.

5 / 5 (2 votes cast)

Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Orphus system