Veeam Cloud Connect Replication (VCC-R) - User Guide


OS Requirements

For VMware replication, maximum ESXi version supported: 6.7.3

For Hyper-V replication: Windows 2016 & Windows 2019 are supported

Network Requirements

Please review the image below to make sure required oubound ports are opened.

Please review the Veeam documentation if needed:

Add Sherweb configuration as a Service Provider

In your Veeam Backup & Replication console, go to Backup Infrastructure to add a Service Provider


Enter the provided server address.

Then, add provided credentials.



Then, your hardware plan will be displayed


If needed, customize the NEA (network extension appliance) for your network.


Follow the remaining steps in the wizard


Create a replication Job to replicate into the Sherweb cloud

In your Veeam Backup & Replication console, create a new replication job.

Enable the Network remapping (as the DR site will have a different virtual network)


Select the virtual machines to replicate to the Sherweb cloud


Then, choose the cloud destination (hardware plan)




Map your network at source and destination sites.

Set your desired retention policy. Then, go to Advanced to set email notifications.



Follow next wizard steps.



Set the desired replication schedule.


Then, you will see your replication job with the Sherweb cloud as the destination.

Review the disk space usage in the Sherweb cloud

In your Veeam Backup & Replication console, go to Backup Infrastructure to find your hardware plan.


If the information is not up-to-date, you can rescan the Service Provider to refresh the information

Configure the failover plan

In your Veeam Backup & Replication console, create a Cloud Connect failover plan.


Name your plan (you can have multiple plans)

Add the replicated virtual machines to include in the failover plan. A delay can be set to start VMs in a specific order (to start a domain controller two minutes before the remaining servers for example)


If needed, customize the gateway section.


Then, add the VMs requiring a mapping rule (like a port forward rule)




Complete the wizard


Then, you plan will appear in the list



You can test the plan, start the plan with the latest recovery point or choose the recovery point to start. 

Don’t start replicated servers manually when it is possible.


Once the plan is completed, replicated servers are up and running and your mapping rules are applied

In the example below, the RDP access is enabled for the replicated VM in the cloud.



To stop the failover plan, click on Undo (that will stop the NEA and all replicated VMs without saving changes.




You can also choose to Failback to production. That means replicating changes from replicated VMs in the cloud to on-prem servers.



If you can’t access your Veeam software to start the plan in case of emergency, use the web portal to manually start replicated virtual machines: