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 16. Protection Groups and Recovery Plans
Creating a recovery plan for each application enables testing and failover of individual
applications. Creating a recovery plan that includes all of the protection groups is useful when
testing or failing over all applications at a site.
NOTE: Concurrently testing or running multiple recovery plans that contain the same protection
group will produce error messages in the Site Recovery Manager.
One of the steps in creating a recovery plan is configuring a test network for each of the
recovery networks at the recovery site. When testing a recovery plan, recovered virtual
machines are connected to a corresponding test network, as defined in a recovery plan. By
default, Site Recovery Manager uses an isolated network - a virtual switch with no external
connectivity that is created dynamically when a recovery plan is tested. This is a simple and
effective approach, but connectivity between virtual machines is limited to the virtual machines
running on the same vSphere host.
Figure 17. Default Isolated Test Network in a Recovery Plan
The default setting, “Isolated network (auto created)”, can be changed to another port group
available at the recovery site. For example, a Virtual LAN (VLAN) can be configured at the
recovery site that is available to all vSphere hosts, but not routed to production networks. This
enables connectivity between virtual machines on different hosts at the recovery site without
interfering with other virtual machines that are not being tested.