Skip to content

Commit ec6e5e9

Browse files
committed
review-5
1 parent ddd106e commit ec6e5e9

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

learn-pr/azure/protect-on-premises-infrastructure-with-azure-site-recovery/includes/2-azure-site-recovery-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@ Several components must be set up to enable Azure Site Recovery:
5050
- **Credentials**: The credentials you use for Azure must have the **Virtual Machine Contributor** and **Site Recovery Contributor** roles to allow permission to modify both the virtual machine (VM) and the storage that Site Recovery is connected to.
5151
- **Configuration server**: An on-premises VMware server fulfills several roles during the failover and replication process. You obtain it from the Azure portal as an open virtual machine appliance (OVA) for easy deployment. The configuration server includes a:
5252
- **Process server**: This server acts as a gateway for the replication traffic. It caches, compresses, and encrypts the traffic before sending it over the WAN to Azure. The process server also installs the mobility service onto all the physical and virtual machines targeted for failover and replication.
53-
- **Master target server**: This machine handles the replication process during a failback from Azure.
53+
- **Main target server**: This machine handles the replication process during a failback from Azure.
5454

5555
> [!IMPORTANT]
5656
> To fail back from Azure to an on-premises environment, VMware vCenter with a configuration server must be available even if you're only replicating physical machines to Azure. You can't fail back to physical servers.

0 commit comments

Comments
 (0)