Part 4 VMware Site Recovery Manager 5 Site Pairing

VMware Site Recovery Manager 5 Site Pairing

In Part 4 of this VMware Site Recovery Manager 5 Tutorial Series, we will be running through the site pairing process of our Primary and Secondary sites.

Pairing Sites within VMware Site Recovery Manager 5

1. Open up your vCenter Server and browse to Solutions and Applications – Site Recovery – your vCenter Server. Click on Sites on the left hand side if it’s not already selected.

2. In the right hand side pane under 1. Connect the Sites, click Configure Connection. Enter in your secondary vCenter Server address. Default port is 80, change it if you need to. Click Next.

3. The Secondary vCenter Server’s Certificate will need to be validated. If you are using an auto generated certificate you will see this message. Click Ok.

4. Type in a username that has administrator credentials on your secondary sites vCenter Server and click Next.

5. This certificate warning is now from your secondary site’s VMware Site Recovery Manager 5. Again if you used an auto generated certificate you will see this message. Click Ok.

6. The site pairing will go through the following steps and once Reciprocity is establish you will have a successful VMware Site Recovery Manager 5 site pairing. Click Finish.

7. These credentials are to connect to the secondary sites Site Recovery Manager 5 instance. Enter in a user that has administrative access to vCenter here, this will also by default give administrative access to VMware Site Recovery Manager 5. Click Ok.

8. Select Install this certificate and click Ignore.

9. As you can see on the left hand side, we can now see our secondary Site named Secondary Site Lab. We have now completed the process for pairing the sites.

Continue onto Part 5 VMware Site Recovery Manager 5 Configuring the Netapp SRA

Disclaimer:
All the tutorials included on this site are performed in a lab environment to simulate a real world production scenario. As everything is done to provide the most accurate steps to date, we take no responsibility if you implement any of these steps in a production environment.