- TMAN-17442: A volume wasn't put into the correct protection group after reprotect. The reprotect workflow will create the source pgroup on the target array with the correct volume in the pgroup. Background: If a datastore that has a protection group that replicates to an array was reprotected, the protection group wasn't created on the target array and the failed over volume was put into PureSRADefaultProtectionGroup instead of the original pgroup.
-
TMAN-18649: While running a reprotect after a successful migration if the reprotect is interrupted by the target SRM server being restarted, when the reprotect is attempted again an error was thrown in the SRM logs. The reprotect workflow will now will now able to recognize the tracking snapshots. Here is an error example:
The remote server returned an error: (400) BAD REQUEST. --> Message from Purity='ctx:PrepareReverse,msg:Name already in use.'
- TMAN-18505: When using ActiveCluster with asyncronous replication to a 3rd array on Purity 6.3+ with SafeMode default protection enabled and SRM, failback from the 3rd array to the stretched pod would fail. The SRM workflow has been optimized to work better with SafeMode.