Today we will continue in our series, before begin this part, lets review what we did in previous parts.
In Part 1, we discuss a general concept about azure site recovery and the discuss the advantages and limitations of each ASR type.
In Part 2, we discussed the requirements for VMware / Physical to Azure ASR, also we discussed the limitations, on-premise requirements, OS supported versions … etc.
In this part we will discuss the implementation of the three servers need to be implemented in order to protect your VMWARE VM’s or physical servers to azure.
As we discussed in part 2, we need three servers, two servers will be deployed in Azure and the third one will be implemented in local environment.
before begin the implementation, let’s review the functionality of these three servers:
Process Server: this server will be deployed in the on-premise environment, it’s recommended to be in the same subnet of the server need to be protected, simply the main functionality of this server is to talk with the mobility service which will be installed on all VMware VM’s or physical servers, the process server will take the data and make some encryption, compression and caching then send the data to the Master target server. Also this server is responsible of the automatic discovery of VMware virtual machines.
- Master Target Server:
It’s deployed in Azure, there is three template of this server available in azure, it can be a windows based or Linux based. simply the functionality of this server to receive all data from the on-premise process server. Both server the config and master one must be in the same virtual network in azure.
- Configuration server: there is no real work on this server, this server is only responsible to manage and coordinate all above mentioned servers, it’s also deployed in Azure. also it’s coordinate the fail-over and fail-back processes.
Now let’e begin the implementation part of these three servers, we will begin with the configuration server which will be deployed in Azure, before start deploying these servers, you need to implement and azure site recovery vault, you can simply imagine this vault as the container which will be hold the Process, Master target and configuration server, this vault must be implemented in the same region of the virtual network, to do this, login to azure portal using https://manage.windowsazure.com, after that go to recovery service and click in (+) button as below:
Choose the ASR vault name, finally choose the region and click on create Vault:
Withing seconds the ASR vault will be ready in the recovery service page, now click in the ASR Vault name:
In the prepare Target Azure resources page, click in deploy configuration server:
The configuration server wizard will appear as below:
Fill the required information and click on the tick button:
Configuration Server Name: This is the host name of the config server.
New User Name: this the local admin on the configuration server.
Password: the local user password.
Network connectivity Type: choose VPN or Public Internet as you need, we will use in this article a VPN since we already setup a VPN between azure and on premise environment.
Microsoft Azure Network: select an existing Network, to learn more review my Network Article.
Subnet: choose the needed subnet.
IP Address: Choose a valid IP address with your subnet.
In Network Connectivity Type, there is two options: the first one is VPN if you already setup a site to site VPN, if you dont want to use a VPN you can choose the second option which is Public Internet but if you choose this option you need to do additional steps not covered in this article.Also if you choose the VPN, the replication will done through the VPN tunnel not public Internet, but once you failover the VM’s to azure you can access the VM’s through the VPN only, which means you cannot access the virtual machines direct from azure portal, but still you can add the endpoints to access it from Azure direct even you choose the VPN type which will cover in last part of this series.
Once you fill all required information, wait a minutes and the configuration server will be ready to use.
Login to the configuration server by access it By IP through VPN, since as we said we cannot access it from portal since we used VPN type, we need to login to config server to register the server in the ASR vault, after you login to the config server, The register wizard will start automatically:
Click in I Accept button:
Choose any valid password, click Next:
If you have any proxy, fill required info and click Next:
Choose the language and click Next:
Choose the installation path and click Install:
A dialog will appear contain the Pass-Phrase, copy the Pass-Phrase and keep it since it will be used to register the Master Target and process server in config server later on.
Now let’s deploy the master target server which must be deployed in azure, from the start page in ASR vault, choose deploy master target:
Now fill all reuired information: the host name, OS version (Windows or Linux) we will use windows in this article, the VM size, User name, Password, Configuration server which we deployed in above steps and finally the IP address:
Once you filled all information , click the tick button and within minutes the Master Target server will be ready:
Now, connect to the master target server bu IP using the VPN, you will see the Host Agent Config app start automatically to register the Master target server in config server, as we said before the config server functionality is just to manage the other servers, so we need to register the target server in the config server and later on the process server in config server, enter the IP address of the config server and the port number (443), and the pass-phrase we got in the registration of the config server, keep the other options as it and click OK.
Now let deploy the Process server which will be deployed in on-premise environment, this server as we mentioned before must be windows server 2012 R2 at least, also you must install VMWARE vSpher CLI 5.5 in the process server first, install the VMWARE vSpher CLI 5.5 from VMWARE site be search it in Google :), once you got the installation, Run the setup file, in Welcome page click Next:
Accept the agreement and click Next:
Choose the installation path and click Next:
Wait a while, the installation will finish:
Now go back to the portal, and from ASR vault page, Click Quick Start > Install Process Server on-premises > Download and install the process server:
login to the process server and copy the downloaded zip file to the server, The zip file contains two installation files:
Unzip the archive and copy the installation files to a location on the server.
Run the Microsoft-ASR_CX_TP_188.8.131.52_Windows* installation file and follow the instructions. This installs third-party components needed for the deployment.
On welcome page click Install:
Then run Microsoft-ASR_CX_184.108.40.206_Windows*, on Welcome Page click Next:
Choose process server, Click Next:
If you will protect Physical server click No, if you want to protect VMware also click Yes, click Next:
Choose the Ethernet card will be used for replication server and click Next:
Enter the IP address of the configuration server, the port number (443) and the pass-phrase wich we already got in above steps, click Next:
Choose the available path which will be used for cache data before replication and will be used to encrypt the data before replicated, as we mentioned it’s recommended to be at least 600 GB available space, since this a demo i have an 236 GB only, Click Install:
Restart the server:
To validate that everything is fine, go to portal in ASR vault page, choose servers and click in confiserver:
You must see your Master target and process server in this page, and both must have healthy status:
In Next Part we will add and register the Vsphere hosts and protect virtual machines, so stay tuned 🙂
Ahmad Yasin in a Microsoft Cloud Engineer and the publisher of
AzureDummies blog. He also hold many certificates in office 365
and windows azure including Developing Microsoft Azure Solutions, Implementing Microsoft Azure Infrastructure Solutions
and MCSA office 365.