Azure: Moving from ASM to ARM with ASR (Part 2) - Recovery Vault

Article
1/17/2024

Create the Recovery Vault

In the portal, search for “recovery” and select following highlighted section:

https://i2.wp.com/www.prof-its.be/wp/wp-content/uploads/2017/01/recoveryservices.png?resize=1024%2C306

fill in the details:

https://i1.wp.com/www.prof-its.be/wp/wp-content/uploads/2017/01/create-vault.png?resize=231%2C259

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 we 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 our server we will select the new A4_v2 as this is the cheapest server with 4 cores (ASR Process server can be pretty CPU intensive)

We 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:

https://i2.wp.com/www.prof-its.be/wp/wp-content/uploads/2017/01/fixip.png?resize=399%2C143

download files

In The Azure Portal, go to the recovery vault -> Configuration Server -> Add Server blade to download the software and registration keys we will need during deployment:

https://i2.wp.com/www.prof-its.be/wp/wp-content/uploads/2017/01/download-software.png?resize=347%2C413 https://i0.wp.com/www.prof-its.be/wp/wp-content/uploads/2017/01/download-software2.png?resize=579%2C253