If you scale out your deployment beyond 200 source machines or if you have a total daily churn rate of more than 2 TB, you must add process servers to handle the traffic volume. We have enhanced the product in 9.24 version to provide in-product guidance on when to set up a scale-out process server. To learn when and how to set up the process server, see [Scale for failback by using additional process servers](vmware-azure-set-up-process-server-scale.md). After you set up the process server, you can migrate source machines to use it.

ms.date: 04/08/2019

- Process server installation directory, Example: C:\Program Files (x86)\Microsoft Azure Site Recovery

title: Set up a process server in Azure to fail back during disaster recovery of VMware VMs and physical servers with Azure Site Recovery | Microsoft Docs'

description: This article describes how to set up a process server in Azure, to fail back from Azure to on-premises during disaster recovery of VMware VMs and physical servers.

By default, when you're replicating VMware VMs or physical servers to Azure using [Site Recovery](site-recovery-overview.md), a process server is installed on the configuration server machine, and is used to coordinate data transfer between Site Recovery and your on-premises infrastructure. To increase capacity and scale out your replication deployment, you can add additional standalone process servers. This article describes how to do this.

Azure Site Recovery automatically identifies if Process Server is approaching it's usage limits and guide you to set up a scale out process server.

|Health Status |Explanation | Resource availability | Recommendation|

|---------|---------|---------|---------|

| Healthy (Green) | Process server is connected and is healthy |CPU and memory utilization is below 80%; Free space availability is above 30%| This process server can be used to protect additional servers. Ensure that the new workload is within the [defined process server limits](#sizing-requirements).

|Warning (Orange) | Process server is connected but certain resources are about to reach maximum limits | CPU and memory utilization is between 80% - 95%; Free space availability is between 25% - 30% | Usage of process server is close to threshold values. Adding new servers to same process server will lead to crossing the threshold values and can impact existing protected items. So, it is advised to [setup a scale-out process server](#before-you-start) for new replications.

|Warning (Orange) | Process server is connected but data wasn't uploaded to Azure in last 30 min | Resource utilization is within threshold limits | Troubleshoot [data upload failures](vmware-azure-troubleshoot-replication.md#monitor-process-server-health-to-avoid-replication-issues) before adding new workloads to same process server OR [setup a scale-out process server](#before-you-start) for new replications.

|Critical (Red) | Process server might be disconnected | Resource utilization is within threshold limits | Troubleshoot [Process server connectivity issues](vmware-azure-troubleshoot-replication.md#monitor-process-server-health-to-avoid-replication-issues) OR [setup a scale-out process server](#before-you-start) for new replications.

|Critical (Red) | Resource utilization has crossed threshold limits | CPU and memory utilization is above 95%; Free space availability is less than 25%. | Adding new workloads to same process server is disabled as resource threshold limits are already met. So, [setup a scale-out process server](#before-you-start) for new replications.

Critical (Red) | Data wasn't uploaded from Azure to Azure in last 45 min. | CPU and memory utilization is above 95%; Free space availability is less than 25%. | Troubleshoot [data upload failures](vmware-azure-troubleshoot-replication.md#monitor-process-server-health-to-avoid-replication-issues) before adding new workloads to same process server OR [setup a scale-out process server](#before-you-start)

A process server selected during Prepare Source step is marked green if

- it is in a connected state

- has sufficient resources (CPU, Memory, Free space) to handle on-going replication workload and is capable to handling at least 30% more of additional workload.