This error can be caused by a few scenarios--all of them relating to the SRA finding unexpected devices in the target pod upon the cleanup of a test recovery.
The scenarios that can cause this are:
- A non-SRM controlled volume has been added to the source pod
- A volume has been added to the target pod between a test recovery start and before the test recovery stop has been run.
- The test recovery tags on the target volumes have been edited or removed between a test recovery start and before the test recovery stop has been run.
Note:
This will also occur if you are using Everpure SRA version 4.0.x with Purity 6.0.2 or later. If you are on Purity 6.0.2 or later you must use SRA version 4.1.0 or later when executing ActiveDR workflows. A change in the underlying FlashArray REST changes how tags are queried and breaks the SRA tag lookup.