Product : Microsoft, Azure Site Recovery/UR40, x86
Feature : Deployment Architecture, Architecture, Design & Deploy
Content Owner:  Herman Rutten
On-premises VMware/Physical Servers:
1 Configuration Server Machine (CSM) per site
x Process Servers
x Master Target Servers
1 Mobility Service per VM

On-premises Microsoft Hyper-V:
1 Site Recovery Provider (SRP) per site
1 Recovery Services Agent (RSA) per host

Azure Public cloud:
On-premises VMware vSphere / Physical Servers:
Microsoft recommends running the Configuration Server Machine (CSM) as a VMware VM that can be deployed from a downloaded OVF template. The CSM runs all on-premises ASR components, which include the configuration server, process server, and master target server.

Configuration server: Coordinates communications between on-premises and Azure, and manages data replication.

Process server: Installed by default on the configuration server. It receives replication data, optimizes it (caching, compression, encryption), and sends it to Azure Storage. The process server also performs automatic discovery of on-premises machines (VMs and/or Physical Servers) and installs ASR Mobility Service on VMs that require protection. Additional, separate process servers can be added to handle larger volumes of replication traffic.

Master target server: Installed by default on the CMS. It handles replication data during failback from Azure. Additional, separate master target servers can be added for failback of larger environments.

The Mobility Service needs to be installed on each VM/Physical Server that requires protection. Microsoft recommends allowing automatic installation of the Mobility Service to be performed from the Process Server.

On-premises Microsoft Hyper-V:
The Site Recovery Provider (SRP) is installed on the System Center Virtual Machine Manager (VMM) server where replication is then orchestrated. In addition a Recovery Services Agent (RSA) needs to be installed on each Hyper-V host.

Microsoft Azure public cloud: