Now that the connection between the Protected and Recovery Site is established, we have also discussed in Part – 2 How to Download SRA, Install SRA, Rescan SRA, Adding an Array Manager, and Enabling an Array Pair. Now time to discuss about deploying the vSphere Replication (VR). The VR infrastructure consists of the following components:
- VRM Server: provides the management of the VR Servers across the ESXi hosts
- VR Server: replicates the virtual machines between sites
vCenter Server Managed IP Address
First we need to configure the vCenter Server Managed IP address. The managed IP address will be used by VRM server to communicate with the extension service on the vCenter Server.
1. In the vSphere Client, go to the Administration menu and select vCenter Server Settings.
2. Go to Runtime Settings and fill in the vCenter Server Managed IP address.
Repeat this step for the Recovery Site as well.
Before deploying the VRM Server, a database must be created. Follow these steps to create database for VRM Server:
- Login and right click Databases and select New Database.
- Provide a suggestive name (i.e. VRMS_DB) and change the owner to i.e. srmadmin. Click OK to create the database.
- Close the SQL Server Management Studio and proceed to the next step.
Deploy VRM Server
Next step is the deployment of the VRM Server which is deployed as a virtual appliance from the SRM Server
1. Connect to the protected site of vCenter Server using vSphere Client.
2. Navigate Home –> Solutions and Applications –> And Site Recovery.
3. Click vSphere Replication in the left pane and make sure the Protected Site is selected. On the left pane under Commands –> Click Deploy VRM Server.
5. Press Next in the Source window of the deployment wizard.
6. In the next step, review the OVF Template Details and press Next to continue.
7. Provide a FQDN name and a location for the VRM Server. Click Next.
10. Provide the Password for the root account, Default Gateway, DNS server, IP Address and Subnet Mask for the appliance. Click Next when ready.
12. Review the settings and click Finish to start the deployment process.
13. When the deployment finishes the VRM Server VM will be powered on.
Remember to deploy a VRM Server instance on the Recovery Site as well. Wait until the VRM Server is fully started before proceeding to the next step.
Configure VRM Server
When the VRM Server for the Protected Site is fully started, you will see the VMware Appliance Management Interface (VAMI) displayed and an URL to manage the VRM Server.
1. Next, click on Configure VRM Server under Commands pane in the Site Recovery Manger.
3. In the Getting Started window, Go to option 1: Startup Configuration. Click on Configuration Page.
5. Select SQL Server as DB Type.
6. Provide the FQDN for the DB Host, in my case the vCenter Server.
7. Leave DB Port to default (1433).
8. Enter the DB Username (i.e. srmadmin) and DB Password.
9. Provide the DB Name (i.e. VRMS_DB) created earlier.
10. Leave the VRM Host value to default.
11. Provide a name for the DB Name.
12. Enter a FQDN for the vCenter Server address and leave the vCenter Server Port to default (80).
13. Enter the vCenter Server Username, Password and e-mail address.
14. Scroll down and click Generate and Install under the Generate a self-signed certificate. You should receive a message stating that the certificate was successfully generated and installed.
15. On the right side under the Actions menu, click the Save and Restart Service button.
16. Wait until the process completes, if successful you will see the following message.
18. Also, you will be presented with a security warning, select Install this Certificate and click Ignore button.
19. Go back to the Site Recovery Manager and verify that the VRM Server is now configured.
Continue to part 4 where we will pair the VRM Servers between the Protected Site and the Recovery Site and we will deploy the VR Servers.
Note :- I have used pictures in this post from SRM book written by Abhilash GB and from blog (http://defaultreasoning.com) by Marek.Z and would like to Thank both of them 🙂