6.1
Table Of Contents
- Introduction
- Requirements
- Evaluation Workflow
- Exercise 1: Pairing Sites
- Exercise 2: Configure Inventory Mappings
- Exercise 3: Configure placeholder datastore
- Exercise 4: Add Array Manager and Enable Array Pair (If Using Array Replication)
- Exercise 5: Create a Protection Group
- Exercise 6: Create a Recovery Plan
- Exercise 7: Testing a Recovery Plan
- Exercise 8: Running a Recovery Plan
- Exercise 9: Reprotect a Recovery Plan and Fail Back
- Exercise 10: Virtual Machine Recovery Properties
- Conclusion
VMware, Inc. 3401 Hillview Avenue Palo Alto CA 94304 USA Tel 877-486-9273 Fax 650-427-5001 www.vmware.com
Copyright © 2015 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellec
tual property laws. VMware products a
re covered by one or more patents listed at http://www.vmware.com/go/patents.
VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions. All other mark
s and names mentioned herein may be trademarks of their respective companies.
Figure 26. Change the Virtual Machine Recovery Settings
NOTE: Changes to virtual machine configuration properties apply to the virtual machine in all
recovery plans. For example, if a virtual machine is configured as a member of priority group 3,
it will appear in priority group 3 in all recovery plans.
In this exercise, there are no specific steps that must be performed. The recommendation is to
read about and experiment with the various settings discussed below to understand the virtual
machine recovery options available in Site Recovery Manager.
Priority Groups
There are five priority groups in Site Recovery Manager. As one might expect, the virtual
machines in priority group 1 are recovered first, then the virtual machines in priority group 2 are
recovered, and so on. This provides administrators one option for prioritizing the recovery of
virtual machines. For example, the most important virtual machines with the lowest RTO are
typically placed in the first priority group and less important virtual machines in subsequent
priority groups. Another example is by application tier - database servers could be placed in
priority group 2; application and middleware servers in priority group 3; client and web servers
in priority group 4.
Dependencies
Virtual machines in the same priority group are started in parallel. There is no startup order
guaranteed within a priority group unless one or more dependencies are defined. A dependency
simply instructs one virtual machine to start before another. For example, a virtual machine
named “acct02” can be configured to have a dependency on a virtual machine named “acct01” -
Site Recovery Manager will wait until “acct01” is started before powering on “acct02”. VMware
Tools heartbeats are used to validate when a virtual machine has started successfully.
Figure 27. Virtual Machine Dependencies