Manage a Scale-out Process Server
Scale-out Process Server acts as a coordinator for data transfer between the Site Recovery services and your on-premises infrastructure. This article describes how you can set up, configure, and manage a Scale-out Process Server.
The following are the recommended hardware, software, and network configuration required to set up a Scale-out Process Server.
Capacity planning is an important step to ensure that you deploy the Scale-out Process Server with a configuration that suites your load requirements. Read more about Scaling characteristics for a Scale-out Process Server.
|Number of CPU cores||8|
|Number of disks||3
- OS disk
- Process server cache disk
- Retention drive (for failback)
|Disk free space (process server cache)||600 GB|
|Disk free space (retention disk)||600 GB|
|Operating system version||Windows Server 2012 R2
Windows Server 2016
|Operating system locale||English (en-us)|
|VMware vSphere PowerCLI version||PowerCLI 6.0|
|Windows Server roles||Do not enable the following roles:
- Active Directory Domain Services
- Internet Information Services
|Group Policies||The following Group policies should not be enabled on the server
- Prevent access to the command prompt
- Prevent access to registry editing tools
- Trust logic for file attachments
- Turn on Script Execution
Note: More information about these group policies can be found here
|Internet Information Service(IIS) Configuration||- No pre-existing Default WebSite
- Enable Anonymous Authentication
- Enable FastCGI setting
- No pre-existing websit/application should be listening on port 443
|Network interface card type||VMXNET3|
|IP address type||Static|
|Internet access||The server should be able to access the following URLs either directly or through a proxy server:
- https://cdn.mysql.com/archives/mysql-5.5/mysql-5.5.37-win32.msi (not required for Scale-out Process Servers)
|Ports||443 (Control channel orchestration)
9443 (Data transport)
Downloading the Scale-out Process Server software
- Log on to the Azure portal and browse to your Recovery Services Vault.
- Browse to Site Recovery Infrastructure > Configuration Servers (under For VMware & Physical Machines).
- Select your configuration server to drill down into the configuration server's details page.
- Click the + Process Server button.
In the Add Process server page, select Deploy a Scale-out Process Server on-premises option from the Choose where you want to deploy your process server drop-down.
Click the Download the Microsoft Azure Site Recovery Unified Setup link to download the latest version of the Scale-out Process Server installation.
The version of your Scale-out Process Server should be equal to or lesser than the Configuration Server version running in your environment. A simple way to ensure version compatibility is to use the same installer bits that you recently used to install/update your Configuration Server.
Installing and registering a Scale-out Process Server from GUI
If you have to scale out your deployment beyond 200 source machines, or a total daily churn rate of more than 2 TB, you need additional process servers to handle the traffic volume.
Check the size recommendations for process servers, and then follow these instructions to set up the process server. After setting up the server, you migrate source machines to use it.
- Launch the Azure Site Recovery UnifiedSetup.exe
In Before you begin, select Add additional process servers to scale out deployment.
In Configuration Server Details, specify the IP address of the Configuration Server, and the passphrase.
In Internet Settings, specify how the Provider running on the Configuration Server connects to Azure Site Recovery over the Internet.
- If you want to connect with the proxy that's currently set up on the machine, select Connect with existing proxy settings.
- If you want the Provider to connect directly, select Connect directly without a proxy.
If the existing proxy requires authentication, or if you want to use a custom proxy for the Provider connection, select Connect with custom proxy settings.
- If you use a custom proxy, you need to specify the address, port, and credentials.
- If you're using a proxy, you should have already allowed access to the service urls.
In Prerequisites Check, Setup runs a check to make sure that installation can run. If a warning appears about the Global time sync check, verify that the time on the system clock (Date and Time settings) is the same as the time zone.
In Environment Details, select whether you're going to replicate VMware VMs. If you are, then setup checks that PowerCLI 6.0 is installed.
In Install Location, select where you want to install the binaries and store the cache. The drive you select must have at least 5 GB of disk space available, but we recommend a cache drive with at least 600 GB of free space.
In Network Selection, specify the listener (network adapter and SSL port) on which the Configuration Server sends and receives replication data. Port 9443 is the default port used for sending and receiving replication traffic, but you can modify this port number to suit your environment's requirements. In addition to the port 9443, we also open port 443, which is used by a web server to orchestrate replication operations. Do not use Port 443 for sending or receiving replication traffic.
In Summary, review the information and click Install. When installation finishes, a passphrase is generated. You will need this when you enable replication, so copy it and keep it in a secure location.
Installing and registering a Scale-out Process Server using command-line
UnifiedSetup.exe [/ServerMode <CS/PS>] [/InstallDrive <DriveLetter>] [/MySQLCredsFilePath <MySQL credentials file path>] [/VaultCredsFilePath <Vault credentials file path>] [/EnvType <VMWare/NonVMWare>] [/PSIP <IP address to be used for data transfer] [/CSIP <IP address of CS to be registered with>] [/PassphraseFilePath <Passphrase file path>]
MicrosoftAzureSiteRecoveryUnifiedSetup.exe /q /xC:\Temp\Extracted cd C:\Temp\Extracted UNIFIEDSETUP.EXE /AcceptThirdpartyEULA /servermode "PS" /InstallLocation "D:\" /EnvType "VMWare" /CSIP "10.150.24.119" /PassphraseFilePath "C:\Users\Administrator\Desktop\Passphrase.txt" /DataTransferSecurePort 443
Scale-out Process Server installer command-line arguments.
|Parameter Name||Type||Description||Possible Values|
|/ServerMode||Mandatory||Specifies whether both the configuration and process servers should be installed, or the process server only||CS
|/InstallLocation||Mandatory||The folder in which the components are installed||Any folder on the computer|
|/MySQLCredsFilePath||Mandatory||The file path in which the MySQL server credentials are stored||The file should be the format specified below|
|/VaultCredsFilePath||Mandatory||The path of the vault credentials file||Valid file path|
|/EnvType||Mandatory||Type of envrionment that you want to protect||VMware
|/PSIP||Mandatory||IP address of the NIC to be used for replication data transfer||Any valid IP Address|
|/CSIP||Mandatory||The IP address of the NIC on which the configuration server is listening on||Any valid IP Address|
|/PassphraseFilePath||Mandatory||The full path to location of the passphrase file||Valid file path|
|/BypassProxy||Optional||Specifies that the configuration server connects to Azure without a proxy||To do get this value from Venu|
|/ProxySettingsFilePath||Optional||Proxy settings (The default proxy requires authentication, or a custom proxy)||The file should be in the format specified below|
|DataTransferSecurePort||Optional||Port number on the PSIP to be used for replication data||Valid Port Number (default value is 9433)|
|/SkipSpaceCheck||Optional||Skip space check for cache disk|
|/AcceptThirdpartyEULA||Mandatory||Flag implies acceptance of third-party EULA|
|/ShowThirdpartyEULA||Optional||Displays third-party EULA. If provided as input all other parameters are ignored|
Create a proxy settings configuration file
ProxySettingsFilePath parameter takes a file as input. Create file using the following format and pass it as input ProxySettingsFilePath parameter.
* [ProxySettings] * ProxyAuthentication = "Yes/No" * Proxy IP = "IP Address" * ProxyPort = "Port" * ProxyUserName="UserName" * ProxyPassword="Password"
Modifying proxy settings for Scale-out Process Server
- Login into your Scale-out Process Server.
- Open an Admin PowerShell command window.
- Run the following command
$pwd = ConvertTo-SecureString -String MyProxyUserPassword Set-OBMachineSetting -ProxyServer http://myproxyserver.domain.com -ProxyPort PortNumber –ProxyUserName domain\username -ProxyPassword $pwd net stop obengine net start obengine
Next browse to the directory %PROGRAMDATA%\ASR\Agent and run the following command
cmd cdpcli.exe --registermt net stop obengine net start obengine exit
Re-registering a Scale-out Process Server
- Connect to the Process Server virtual machine using Remote Desktop Connection.
You can launch the cspsconfigtool.exe by clicking on the shortcut available on the desktop. (The tool will be automatically launched if this the first time you are logging into the process sever).
- Configuration Server's fully qualified name (FQDN) or IP Address
- Port on which the Configuration server is listening on. The value should be 443
- Connection Passphrase to connect to the configuration server.
Data Transfer port to be configured for this Process Server. Leave the default value as is unless you have changed it to a different port number in your environment.
- Click the save button to save the configuration and register the Process Server.
- Next open an Admin command prompt.
- Browse to the directory %PROGRAMDATA%\ASR\Agent and run the command
cdpcli.exe --registermt net stop obengine net start obengine
Upgrading a Scale-out Process Server
- Login to the process server as an Administrator.
- Download the latest version of the Unified Setup.
- Double-click the installer to launch the update process.
- The installer will detect the various components that are installed and upgrade them to the latest version.
Decommissioning a Scale-out Process Server
- Ensure that:
- Configuration Server's connection state shows as Connected in the Azure portal
- Process Server's is still able to communicate with the Configuration server.
- Log in to the process server as an administrator
- Open up Control Panel > Program > Uninstall Programs
- Uninstall the programs in the sequence given following:
- Microsoft Azure Site Recovery Configuration Server/Process Server
- Microsoft Azure Site Recovery Configuration Server Dependencies
- Microsoft Azure Recovery Services Agent
It can take up-to 15 minutes for the Process Server deletion to reflect in the Azure portal.
If the Process server is unable to communicate with the Configuration Server (Connection State in portal is Disconnected), then you need to follow the following steps to purge it from the Configuration Server.
Unregistering a disconnected Scale-out Process server from a Configuration Server
The steps to unregister a process server differs depending on its connection status with the Configuration Server.
Unregister a process server that is in a connected state
- Remote into the process server as an Administrator.
- Launch the Control Panel and open Programs > Uninstall a program
- Uninstall a program by the name Microsoft Azure Site Recovery Configuration/Process Server
- Once step 3 is completed, you can uninstall Microsoft Azure Site Recovery Configuration/Process Server Dependencies
Unregister a process server that is in a disconnected state
Use the below steps should be used if there is no way to revive the virtual machine on which the Process Server was installed.
- Log on to your configuration server as an Administrator.
- Open an Administrative command prompt and browse to the directory
Now run the command.
perl Unregister-ASRComponent.pl -IPAddress <IP_of_Process_Server> -Component PS
- This will purge the details of the process server from the system.
Sizing requirements for a Scale-out Process Server
|Additional process server||Cache disk size||Data change rate||Protected machines|
|4 vCPUs (2 sockets * 2 cores @ 2.5 GHz), 8-GB memory||300 GB||250 GB or less||Replicate 85 or less machines.|
|8 vCPUs (2 sockets * 4 cores @ 2.5 GHz), 12-GB memory||600 GB||250 GB to 1 TB||Replicate between 85-150 machines.|
|12 vCPUs (2 sockets * 6 cores @ 2.5 GHz) 24-GB memory||1 TB||1 TB to 2 TB||Replicate between 150-225 machines.|