In this blogpost we will show how to enable the recovery vault and how to install the process server.
Open communication ports
Before we continue, we need to make sure all required communication ports (443 & 9443) are open on all source resources so that they can communicate and replicate with the process server. These ports need to be open on:
– ACL’s (if any)
– Network Security Groups (if any)
– Windows Firewall (enabled by default)
Install the process server
As soon as this is in place we can start with the deployment of the Process server itself, depending on the workload you will need to select a VM size that is appropriate to handle the load.
For small scopes like this POC, a minimum is 2 vCPU and 4GB of memory.
For my server I will select the new A4_v2 as this is the cheapest server with 4 cores (ASR Process server can be pretty CPU intensive)
I already have a management network in ARM where I will deploy this server to, in a later phase we will connect this VNET with the VNET in ASM so that we have direct communication over the Azure Network backbone. (What we call VNET Peering)
Go to the network adaptor settings of the process server and change IP assignment setting to fixed:
Install the process server software
Once logged into the newly created VM we can start installing the process server software:
Select the file that you downloaded from the portal
don’t mind the warnings here as it is a POC, for production enviroments it’s highly advisable to provide enough capacity.
enter the SQL server SA password.
IMPORTANT: to fail over from Azure to Azure, you must use the physical server to Azure failover mechanism!
Clicking Finish will show some additional windows:
save the key to notepad and store the document in a safe place
add the local administrator account(s) of the source servers.
Close and reboot your server now!
You can verify if your server is known in your vault:
Stay tuned for the next chapter: create VNET peering
part 3: Network Configuration