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](vmware-azure-manage-process-server.md#process-server-selection-guidance) on when to set up a scale-out process server. [Set up the process server](vmware-azure-set-up-process-server-scale.md) to protect new source machines or [balance the load](vmware-azure-manage-process-server.md#balance-the-load-on-process-server).

ms.date: 04/23/2019

From 9.24 version, enhancements are made to provide [in-product guidance](vmware-azure-manage-process-server.md#process-server-selection-guidance) on when to set up a scale-out process server. This is to avoid process server throttling and avoid usage of unhealthy process server.

Azure Site Recovery automatically identifies if Process Server is approaching its usage limits. Guidance is provided when 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](vmware-azure-set-up-process-server-scale.md#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. It is advised to [setup a scale-out process server](vmware-azure-set-up-process-server-scale.md#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 **OR** [setup a scale-out process server](vmware-azure-set-up-process-server-scale.md#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](vmware-azure-set-up-process-server-scale.md#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](vmware-azure-set-up-process-server-scale.md#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](vmware-azure-set-up-process-server-scale.md#before-you-start)

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

title: Set up a scale-out process server during disaster recovery of VMware VMs and physical servers with Azure Site Recovery | Microsoft Docs'

description: This article describes how to set up scale-out process server during disaster recovery of VMware VMs and physical servers.

ms.date: 4/23/2019

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 setup a scale-out process server.

From 9.24 version, guidance is added during selection of process server for new replications. Process server will be marked Healthy, Warning and Critial based on certain criteria. To understand different scenarios that can influence state of process server, visit [process server selection guidance](vmware-azure-manage-process-server.md#process-server-selection-guidance).