Test Recovery from a Pod to Asynchronous Target Site

One of the primary benefits of Site Recovery Manager is the ability to test recovery plans-coordinating the failover of the replication and recovery of virtual machines without affecting the configuration, state, protection, or connectivity of the original source VMs.

1. Issue a synchronization of the relevant FlashArray volumes to the target
2. Create new FlashArray volumes from the replicated snapshots on the target array
3. Connect the volumes to the appropriate hosts and/or host groups
4. Rescan the target cluster(s)
5. Resignature and mount the datastores
6. Power-on the VMs and configure them according to the recovery plan

   To initiate a test, click the Test button in SRM.

   

   A wizard will appear, with a default option called Replicate recent changes to recovery site selected.

   

   If this is selected, the SRA will create a new replication point-in-time. If it is de-selected, the SRA will just use the latest point-in-time found for each volume. Note though that during failover, the SRA will always use the latest available point-in-time. So if the SRA creates a new one for the test, and between the completion of that point-in-time and before creating the recovery volumes a new point-in-time is created, that new one will be used for recovery.

   Click Next.

   

   Confirm the test and click Finish.

   If "replicate recent changes" was selected, the SRA will initiate a new point-in-time on the target array and the SRA will give the protection group snapshot created a name including a UUID and the suffix of -puresra.

   

   Note:

   The SRA will create a new replication point-in-time and will apply the retention policy specified in the protection group to it. The protection group snapshot will be destroyed and eradicated according to the schedule. If preferred, manually destroying/eradicating it earlier than the retention policy dictates is allowed.

   The SRA will then create one new volume for each protected volume on the target array with the original name of the volume plus a suffix of -puresra-testFailover.

   

   Note:

   Note that the recovery volumes will not be in a pod, since periodic replication does not support a pod as a target, the volumes are replicated to and recovered in the root of the array (not in any pod).

   They will then automatically be connected to the appropriate hosts and/or host groups. SRM will then rescan the cluster and the datastores will be resignatured and mounted.

   

   Note that the datastores will have the prefix applied to their names of "snap-XXXXXXXX" by SRM. This can be automatically removed by enabling the advanced SRM setting described in SRM User Guide: Site Recovery Manager Advanced Options.

   The VMs will be registered and configured according to the recovery plan.

   

   Note:

   Do not rename the test failover volumes during the test-this will cause them to not be cleaned up and you will need to destroy them manually.