Known Issues

1. ActiveDR
   1. If there are volumes in an ActiveDR pod that are presented to the VMware environment but not in use as an RDM or a VMFS a recovery will succeed but a subsquent reprotect will fail. To complete the reprotect the volumes should be removed or manually tagged.
   2. If a source pod is already demoted when a planned migration recovery is attempted the process will fail and a disaster recovery is required or the source pod must be manually promoted before the recovery can be re-attempted.
   3. Non-VMware volumes cannot be in an ActiveDR pod controlled by SRM. All volumes in the pod must be present and in use as an RDM or VMFS in the VMware environment connected to the SRM pair.
2. ActiveCluster
   1. Pods protected by SRM cannot be renamed. ActiveDR pods can be renamed. Pods in use with ActiveCluster to third site cannot be renamed.
   2. Failback or reprotect from an asynchronous target into a stretched pod is not supported. Pods much be first unstretched before a failback from an asynchronous distance target.
3. General
   1. Volume names must be less than 42 characters in length except for ActiveDR volumes--these can be up to full supported length of the FlashArray
   2. At this time Pure Storage will not support protecting non-vVol FlashArray Volumes that are in Volume Groups. Any support offered by Pure will be best effort. The reason for this is that there are several caveats when using vgroups with SRM that could lead to DR Failovers failing, there has not been enough testing in each of these edge case situations, and getting back into a good state often times requires removing both the Array and SRM protection groups to start from a clean start. This can be both time consuming and leave VMs in an unprotected state. Thus the decision not to recommend the use of vgroups with SRM. This will be resolved in a future SRA release.
   3. Best practice and recommendation from Pure Storage is to place volumes in protection groups for use with SRM protection groups and recovery plans. Using Hosts or Host Groups as placement for volumes to be protected by SRM has inconsistent behavior and support for this would be best effort. Pure Storage is working to improve these workflows for a future release of the SRA when using host or host groups, but at this time Pure would recommend to avoid using Host or Host Group placement for FlashArray protection groups.
   4. If either FlashArray has been renamed after they have been connected, all test failovers, failovers and reprotects will not execute completely. The is due to the array pair naming not getting updated if either array is renamed (if purearray list --connect is ran from the CLI, the previous names will show). Should an array be renamed, the recommend remediation if using only async replication is to disconnect the FlashArrays and reconnect them. Should ActiveCluster be enabled, the recommended remediation is to run through the purearray connect process from the array that had the connection initiated from initially.
   5. There is an uncommon situation where the replication of a protection group snapshot completes in the middle of a test recovery or recovery operation leading to different point-in-time snapshots being chosen for two or more volumes. This will be fixed in the next patch release.