Loading...

 

Error

Your web browser doesn't support some required capabilities.

This demo works best with the latest version of Chrome, Firefox, or Safari. IE 9+ also sort of works...

This simulation works best with the latest version of Chrome, Firefox, or Safari. IE 9+ also sort of works...

Error

This demo file is incomplete or damaged. Please reload the page, or download again:

For VMware partners:
www.vmware.com/go/partnerdemos

For VMware employees:
www.vmware.com/go/demos

This simulation did not load correctly. Please reload the page.

Error

Visit the VMware Demo Library
to get more demos!

For VMware partners:
www.vmware.com/go/partnerdemos

For VMware employees:
www.vmware.com/go/demos

The demo will restart in 5 seconds.

Hit Esc to cancel

X
↩ RETURN TO THE LAB
HOL-1805-01: Site Recovery Manager Configure and Test

This is an interactive demo

Drive it with your mouse, your finger, or just use the arrow keys.

Use Learn mode to learn the demo. The orange boxes show where to click.

Use Present mode to hide the orange boxes and notes.

Use Autoplay mode to make it play like a movie. Hit the Esc key to stop.

Click a Shortcut to jump to a specific part of the demo.

X
Copyright © 2017 VMware, Inc. All rights reserved.
Hide notes
Restore notes
Open notes window
Increase font size
Decrease font size

This part of the lab is presented as a Hands-on Labs Interactive Simulation. This will allow you to experience steps which are too time-consuming or resource intensive to do live in the lab environment. In this simulation, you can use the software interface as if you are interacting with a live environment.

The orange boxes show where to click, and the left and right arrow keys can also be used to move through the simulation in either direction.

This will show how features in Site Recovery Manager can be used to:

  • Protect virtual machines using storage policies
  • Utilize stretched storage and cross-vCenter vMotion to non-disruptively move VMs between sites
  • Use NSX to simplify network mapping.

We will start off discussing NSX and network mapping, run a recovery plan in planned migration mode to utilize cross-vCenter vMotion, run it again in disaster recovery mode, then walk through a recovery plan test and conclude with utilizing a storage policy to protect a VM.

SRM NSX Integration

NSX supports creating Universal Logical Switches, which allow for the creation of layer-2 networks that span vCenter boundaries. This means that when utilizing Universal Logical Switches with NSX there will be a virtual port group at both the protected and recovery site that connect to the same layer-2 network

When virtual machines are connected to port groups that are backed by Universal Logical Switches, Site Recovery Manager will automatically recognize this and not require manual network mapping between the protected and recovery locations. Site Recovery Manager intelligently understands that it is logically the same network on both sites and thereby automatically links the protected and recovery networks.

To demonstrate this, note the lack of any network mappings within Site Recovery Manager and because of the use of NSX Universal Logical Switches, the lack of any recovery issues in the remainder of this lab.

  1. Click the menu button, then click VMs and Templates
  2. Notice that the VM selected is using a ULS connected network
  3. For later labs, note that we have 2 clusters/sites: P (Primary/New York) and S (Secondary/New Jersey). All our VMs are currently running at the Primary site
  4. Click the menu button, click Site Recovery, then click Sites
  5. Note the lack of any network mappings. In the next steps we will see how even without network mappings failovers proceed normally and VMs are still connected to the relevant network after failover.
  6. Click the previous page/Site Recovery button

Orchestrated cross-vCenter vMotion  Running and Testing Recovery Plans

This section will run through different recovery plan workflows to see how SRM 6.5 interacts with stretched storage to provide enhanced availability. Start by running the ERP recovery plan in planned migration to observe the cross-site vMotion functionality.

  1. Click Recovery Plans
  2. Click the red Run recovery plan button
  3. Click the checkbox indicating understanding that this will permanently alter the environment
  4. Note that Recovery Type is set to Planned Migration and the Enable vMotion of eligible VMs is selected.
  5. Click Next, then click Finish
  6. Observe the recovery plan running.
  7. Click step 5 to expand additional detail, then click step 5.1 and click step 5.1.3.
  8. Note that as it is configured in our Recovery Plan, the database servers (ERP-DB01 & 02) are being migrated first, followed by the application servers and lastly the web servers.
  9. Click Recent Tasks to observe the vMotion tasks
  10. Click Recent Tasks again to minimize the recent tasks window.
  11. Scroll down to observe the remainder of the recovery plan.
  12. Now that the ERP application has been non-disruptively migrated to the secondary/New Jersey site, click the reprotect icon to protect it back to the primary/New York site
  13. Click the checkbox to confirm understanding that the operation can’t be undone
  14. Click Next, then click Finish.
  15. Observe the completion of the reprotection workflow. The recovery plan is now ready to be used again
  16. Click the menu button and click VMs and Templates to confirm that the ERP VMs are now running in the secondary/New Jersey site

Now that the ERP application is running and protected at the Secondary/New Jersey site it is important to run a test of the recovery plan prior to failing back to the Primary/New York site.

  1. Click the previous page/Recovery Plans button
  2. Click the ERP Recovery Plan again and click the green Test Recovery Plan button.
  3. Click Next, then click Finish
  4. Observe the Test workflow running.

Now that it is complete we can view the Test VMs running at the recovery site which now is Primary/New York

  1. Click the menu button, then click VMs and Templates
  2. Observe that the ERP VMs now appear in both locations. The VMs at the Primary/New York site are the test VMs.
  3. Assume we have run any needed application tests and are ready to clean up the test.
  4. Click the previous page/Recovery Plans button
  5. Click the Cleanup button to power off and delete the test VMs and return the recovery plan to a ready state
  6. Click Next, then click Finish
  7. Observe the Test workflow running/completing
  8. Click the menu button and click VMs and Templates to confirm the test VMs have been cleaned up

Some time has passed and now the Secondary/New Jersey site suffers an outage requiring us to recover the ERP application at the Primary/New York site. When a recovery plan is run in disaster recovery mode it doesn’t utilize cross-vCenter vMotion, rather it recovers VMs similarly to how SRM always has. This provides orchestrated recovery to a multi-site stretched storage environment, something which was unavailable in prior versions of SRM.

  1. Click the previous page/ERP button
  2. Click the run recovery plan button
  3. Click the checkbox indicating understanding that this will permanently alter the environment
  4. Change the recovery type to Disaster Recovery. Note that this greys out the vMotion option.
  5. Click Next, then click Finish
  6. Note that the Live Migration of VMs step is skipped
  7. Now that the ERP application has been recovered to the primary/New York site, click the reprotect button to protect it back to the secondary/New Jersey site
  8. Click the checkbox to confirm understanding that the operation can’t be undone
  9. Click Next, then click Finish. Observe the completion of the reprotection workflow
  10. The recovery plan is now ready to be used again
  11. Click the menu button and click VMs and Templates to confirm that the ERP VMs are now running in the primary/New York site

Storage Policy Based Protection

Policy based protection allows for the protection of a VM simply by associating it with a policy and placing it onto storage that is in compliance with that policy. Follow these steps to protect the FIN-Web02 VM in the Finance Protection Group.

  1. Click the Fin-Web02 VM
  2. Click Actions, Migrate...
  3. Click Change storage only then click Next
  4. Click the VM Storage Policy dropdown and select Non-Stretched Storage
  5. Note that in the datastore selection window datastores are now separated into compatible and incompatible and a compatible datastore is already selected. Click Next, then click Finish
  6. The Fin-Web02 VMs storage is now being migrated. Click on the previous page/Protection Groups button and note that the Fin-Web02 VM has been automatically added to the protection group

 To return to the lab, click the link in the top right corner or close this browser tab.