6.1

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 18. Portgroup Configured as the Test Network in a Recovery Plan
Recommendation: When implementing Site Recovery Manager in a production environment,
utilize a dedicated VLAN at the recovery site for recovery plan testing. This VLAN should be
available to all vSphere hosts at the recovery site, but routing should not be enabled to any
other networks to prevent interference with workloads outside of the Site Recovery Manager
test environment. This is not a requirement for evaluation.
Additional virtual machine recovery properties can be configured such as creating virtual
machine dependencies, adding visual prompts, and changing IP addresses. Virtual machine
recovery properties will be covered in a later exercise.
See Create a Recovery Plan in the Site Recovery Manager documentation.
Exercise 7: Testing a Recovery Plan
After creating a recovery plan, it is beneficial to test the recovery plan to verify it works as
expected. Site Recovery Manager features a non-disruptive testing mechanism to facilitate
testing at any time. It is common for an organization to test a recovery plan multiple times after
creation to resolve any issues encountered the first time the recovery plan was tested.
Verify the recovery plan is ready for testing or running by checking the “Plan status”. It should
show “Ready”. Click the green arrow below “Description” to begin the test process.
Figure 19. Test Recovery Plan
When testing a recovery plan, there is an option to replicate recent changes, which is enabled
by default. Replicating recent changes will provide the latest data for the testing process.
However, it will also lengthen the amount of time required to recover virtual machines in the
recovery plan, as replication has to finish before the virtual machines are recovered.