Monday, February 16, 2015

USE VMware SITE RECOVERY MANAGER TO TEST DISASTER RECOVERY -1

Scenario:

In working with the business, IT has determined that they will protect the application with the following policy in mind.
All workloads in Production DC will be protected and recovered using resources in the DR DC
All workloads in DR DC will be protected and recovered using resources in the Production DC
vSphere Replication will be used to protect all workloads to save cost since a recovery point objective of 15 minutes is acceptable for all Customer  data.

ENSURE VMS ARE BEING REPLICATED SUCCESSFULLY

We need to review the status.
1. Click on vSphere Replication in the left pane
2. Click on vc-01b.corp.local to select the local vCenter
3. Click on Monitor

VIEW VSPHERE REPLICATION STATUS

1. Make sure you have Outgoing Replications selected
2. View the status of outgoing VM replications. All should have "OK" as their status and have vc-01a.corp.local as their target. The status for some VMs may show an RPO violation instead of "OK". This is because of the way the Hands-On Labs are configured and can be ignored.
3. Click on Home when you are done viewing the information on this page.

From the Home page of the vSphere Web Client, click on Site Recovery on the left pane of the client. This will open the Site Recovery home page.

We need to verify that the two sites, DR DC and Production DC, are paired correctly and connected. Click onSites to view information about the SRM pairings



VERIFY SITE PAIRING



You should see the two sites, DR DCand Production DC, listed in the left pane of the client. Now you should verify that the sites are paired and connected.

1. Click on Production DC

Now you are viewing the Summary page for Production DC. The local site is Production DC and the paired site is DR DC.
1. Make sure you're viewing the Summary tab.
2. Verify that the Client and Server Connection status for Production DC is "Connected."
3. Verify that the Client and Server Connection Status for DR DCis "Connected"
4. Optionally, you can view the same information from the perspective of the paired site. Click on DR DC in the left pane and you should see the same information displayed fromthat site's perspective.

5. When you're done, click on Site Recovery to be taken back to the main Site Recovery page.


REVIEW RECOVERY PLAN SETTINGS


We now need to view the details of our disaster recovery plan and verify that it takes into account the dependencies between VMs.  Click onRecovery Plans to see how the VMs will be recovered in DR DC

SELECT THE RECOVERY PLAN

.Click on the Customer Care Web App recovery plan

Our web application consists of three virtual machines, a tier 1 web server, tier 1 database server, and an extranet server the business considers tier 2.  We need to make sure the VMs are in their appropriate groups.
1. Select the Monitor tab
2. Click on Recovery Steps
3. Expand Step 6 by clicking on the arrow next to orange step 2.
It appears that the VMs are all in the same tier! If all three VMs are started at the same time then the application may not work correctly. The plan will need to be modified to ensure that the application is recovered in the correct order so that the Database and Web Server VMs are starting up before the Extranet Server.
Reconfigure virtual machine start-up order

1. Right-click on DB Server
2. Select All Priority Actions
3. Select Priority 1
Click "Yes" when asked if you want to change the priority group. Virtual Machines can be part of multiple recovery plans and changing this change will impact any recovery plan that this VM is a member of.
Repeat these actions for the Web Server so that it is also in the Priority 1 group.


Test disaster recovery plan

Now that you have reviewed the SRM configuration and verified that the recovery plan is correct, you can test the plan at any time to ensure that it will function as required.

Navigate to the Recovery Plans page that you previously visited
1. The "Customer Care Web App" recovery plan should be highlighted as it appears in this screenshot. If it is not, click on it once to highlight it.
2. Click the green arrow to initiate a test

 . Verify that the Protected Site and Recovery Site are correct.
2. Make sure the "Replicate recent changes to recovery site" checkbox is NOT checked.
3. Click Next
4. Click Finish on the next screen.


Click on the "Customer Care Web App" recovery plan to monitor the test progress. The test may take several minutes.
1. Select the Monitor tab.
2. Make sure that you've selected
When all steps have completed, the Plan Status will be Test Complete.

You can optionally now login to the DR DC vCenter and navigate to the VMs and Templates screen to see that the VMs are in fact running. Open a new tab in your browser and click on the DR DC vCenter bookmark. Click the "Use Windows session authentication check box and log in. Open the Hosts and Clusters view.
Take a look and verify...
1. The VM has started
2. VMware Tools is running
The VM is connected to an SRM created test bubble port group. This port group is not connected to any physical uplinks and is created by SRM when the test plan is run. It will be deleted when the test is complete. Alternatively, you could have built a dedicated test network for a more in depth disaster recovery test.


Clean up activities from disaster recovery test

Switch back to the Production DC vSphere client. Now that we have verified that the Customer Care Web App can be successfully recovered in DR DC, it is time to clean up the test
1. Click the Cleanup button to initiate the cleanup process

1. Click Next to confirm the cleanup options. The "Force Cleanup" check box will be grayed out
2. Click Finish to initiate the cleanup

In the next blog, we will cover Return to normal operations - fail back the application from dr dcto production dc


No comments:

Post a Comment

Featured Post

Amazon Route 53

Amazon Route 53 is a highly available and scalable Domain Name System (DNS) web service.Route 53  perform three main functions in any...