Home > Storage > PowerMax and VMAX > Storage Admin > Implementing Dell SRDF SRA with VMware SRM > Recovery
SRM recovery plans, whether they are for migration or recovery, run as part of a planned workflow that ensures that systems are properly shut down and that data is synchronized with the recovery site prior to migration of the workloads. This ensures that systems are properly quiesced and that all data changes have been completely replicated prior to starting the virtual machines at the recovery site. If, however, an error is encountered during the recovery plan execution, planned migration will stop the workflow, providing an opportunity to fix the problem that caused the error before attempting to continue.
All recovery plans in SRM include an initial attempt to synchronize data between the protection and recovery sites, even during a disaster recovery scenario. During a disaster recovery event, an initial attempt will be made to shut down the protection group’s virtual machines and establish a final synchronization between sites. This is designed to ensure that virtual machines are static and quiescent before running the recovery plan, to minimize data loss where possible during a disaster. If the protected site is no longer available, the recovery plan will continue to execute and will run to completion even if errors are encountered. This minimizes the possibility of data loss while still enabling disaster recovery to continue, balancing the requirement for virtual machine consistency with the ability to achieve aggressive recovery-point/time objectives.
Figure 104 shows the recovery plan execution wizard.
Figure 104. Recovery plan execution wizard in SRM
Note: If the advanced option, ReverseReplicationDuringRecovery is enabled the recovery site SRA will perform all reprotect operations relating to SRDF reconfiguration during the recovery process and reprotect will therefore only perform recovery plan/protection group swaps. Refer to the section Reprotection for information on what operations are executed during recovery when this option is enabled.
Note: Though SRDF relationships are possible with a larger R2 device, it will prevent certain SRDF operations such as reprotect and swap and therefore should only be considered if the SRM setup is for migration purposes only.