Veeam Cloud Connect Replication (VCC-R) - User Guide
TABLE OF CONTENTS
- OS Requirements
- Network Requirements
- Important Notes
- Add Sherweb configuration as a Service Provider
- Create a replication Job to replicate into the Sherweb cloud
- Review the disk space usage in the Sherweb cloud
- Configure the failover plan
For VMware replication, maximum ESXi version supported: 6.7.3
For Hyper-V replication: Windows 2016 & Windows 2019 are supported
Please review the image below to make sure required oubound ports are opened.
Please review the Veeam documentation if needed: https://helpcenter.veeam.com/docs/backup/cloud/ports.html?ver=110
- For a Site-to-Site VPN setup the DR site, the included Network Extension Appliance (NEA) will not be sufficient. Please request the setup of the appliance of your choice with your Veeam Cloud Connect Replication (VCC-R) service to your account manager. Additional fees apply. By using your own appliance in the DR site, you will also have to manage mapping rules (if any) inside the appliance.
- Avoid powering on a replica manually — this may disrupt further replication operations or cause loss of important data.
- If you can’t access your Veeam software to start the failover plan(s) in case of emergency, use the Veeam Cloud Connect Replication (VCC-R) portal to manually start replicated virtual machines in the cloud: https://vcccan01portal.yourcloudservers.com
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 replicated virtual machines to include in the failover plan.
A delay can be set to start VMs in a specific order (Example: to start a domain controller three (3) minutes before remaining servers)
If needed, customize the gateway section.
Then, add VMs that require a mapping rule (like a port forward rule)
Complete the wizard
Then, you plan(s) will appear in the list
To test the failover plan, start the plan with the latest recovery point or choose the recovery point to start. It's the same procedure for a real disaster recovery.
Once the plan startup is completed, replicated servers are up and running and your mapping rules are applied (the Network Extension Appliance (NEA) also started with VMs).
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 Network Extension Appliance (NEA) and all replicated VMs without saving changes.
You can also choose to Failback to production. That means that changes made in replicated VMs in the cloud will be replicated to source on-prem servers.
Once the failback is completed, validate if all changes performed in replicated VMs are now in on-prem servers. If servers start normally and all changes were successfully replicated from the cloud VMs to the on-prem servers, you can now commit the failback with the Commit Failback button.