Specifications

32
hosts may be required for DR testing just as with the original failover setup.
14. Verify that the SnapMirror relationship has completed transferring and that it is up to date.
15. Perform a SnapMirror update if necessary and perform a test run of the recovery plan.
16. When the recovery plans and other necessary infrastructure have been established at the primary site,
schedule an outage to perform a controlled failover.
17. When appropriate, notify the users of the outage and begin executing the failback plan.
18. During the scheduled failback, if allowed to do so, SRM will shut down the virtual machines at the DR
site when the recovery plan is executed. However, this is not desired in most cases. Instead of allowing
SRM to shut down the virtual machines, perform a controlled proper shutdown of application and
infrastructure virtual machines at the DR site. This helps make sure that all applications are stopped,
users are disconnected, and no changes are being made to data that would not get replicated back to
the primary site.
19. Once the environment to be failed back is properly shut down, perform a final SnapMirror update to
transfer any remaining data back to the primary site.
20. Execute an SRM recovery plan in the opposite direction as was done in the disaster recovery.
21. Verify the recovered environment and allow users to connect and continue normal business operations.
22. Reestablish primary-to-DR replication.