The Process Server is the most important component in a deployment like ours. It is the one responsible for handling all compute and IO intensive aspects of replication and maintaining replication policies, replication status and health reports.
In the previous parts for this series:
Network Security Group (NSG) Rules
Before starting with the installation, we need to add some inbound and outbound rules to the VM network security group (NSG). This is important since the Mobility Service that we will install later on our Classic VM, needs to communicate with the Process Server over ports 443 & 9443 (TCP).
By default, every Windows VM in Azure deployed with Windows FW On, make sure you are allowing those ports over there as well, in my case I’m just disabling it (and the User Account Control as well).
Process Server Installation
Finally, we can start with the server installation using the files we have downloaded from the Vault in the previous post. The installation is pretty straight forward and will install MySQL database followed by the application.
Since this a PoC deployment, I’m going to ignore the storage capacity requirement of at least 600GB of free space – someone is paying for those resources you know 🙂
The whole purpose of this blog post series is to show how to convert Classic VM to an ARM one. In order to do that, we need to make the Process server “think” that the VMs it’s working against for replication and eventually an unplanned failover are physical boxes. We are not going to protect VMware VMs at this point.
Again, ignoring the 600GB thing.
Point the installation to the registration key downloaded from the Recovery Services Vault.
Hit the Install button and kick back, this will take few minutes.
Wait with the reboot, it’s easier for us to create the Mobility Service installation account.
Once the installation has finished save the Connection Passphrase to a txt file. Every Mobility Service Agent needs this string in order to get registered against the server.
Next, we need to create a local admin account which will have the authorization to install and register the protected server (Classic VM) Mobility Service against the Vault. In my case, my protected VM is not a domain member so I will just create a standard local admin account. In case you need to, multiple accounts can be created.
That’s it for the Process server installation, you can go ahead and restart the server.
In order to verify that the Vault registration has completed successfully, go to the Management Servers in the Vault and select “Site Recovery servers”.
In the next part for this series, we will install the Mobility Service on our Classic VM.