Failed to reverse replication for failed over devices. Cannot process consistency group 'peer-of-e184134e-5a94-9f76-5c53-ae33e6df93d5' with role 'target' when expected consistency group with role 'promotedTarget'.
SRA command 'discoverDevices' failed. More than one type of devices found in the pod. Please verify that all the volumes are either untagged or tagged with same value in the "puresra" namespace.
As of the 4.0 release of the SRA it is not supported to have a volume that is not in use as a VMFS or a RDM in vCenter environment controlled by the SRM pair. Having volumes that are not in use, or are in use in a different vCenter environment, or in use in a non-VMware environment cannot be in the same pod as volumes controlled by SRM.
It is also not supported to provision a new datastore or RDM into the an ActiveDR pod between a recovery and a reprotect.
While violating these requirements will not prevent failover, they will prevent a successful test recovery cleanup, and the reprotect operation. A reprotect will fail with the above error message.
Or you will see this error in a device discovery:
In this case, there is an extra volume in the pod:
That was provisioned after the recovery was completed--this is evidenced by the fact that it does not have the puresra-failover tag on it:
Note that for this failure running a forced reprotect will not work--this process will only work for certain VMware-side failures, not SRA failures on device state changes.
But there are options, but it depends on what the issue is.