Fixed Issues

1. ActiveDR
   1. ActiveDR failover did not work in Purity 6.0.2 and later due to an internal API change. This has been resolved and the 4.1.0 SRA support ActiveDR in all Purity releases.
   2. A warning like "Expected consistency group not found in SRA's 'queryReplicationSettings' response during test and recovery no longer appears. This was an innocuous failure due to not supporting the queryReplicationSettings command for ActiveDR workflows. This API is now implemented.
   3. Deprecation of the usage of the puresra-demoted tag in ActiveDR workflows which was deemed to be unnecessary. The only tags will be puresra-failover and puresra-testFailover.
2. Discovery:
   1. Device discovery logs are less verbose, which in larger environments could exhaust logging directory capacity needlessly.
   2. Removal of an error in device discovery if overly long volume names are present which gives a false impression of failure (a warning is returned instead in the SRA logs).
   3. Replicated vVols are now filtered out during a deviceDiscovery operation and will not be returned to SRM via the SRA.
3. General:
   1. Recoveries that were partially successful (some volumes were connected and others were not) can lead to a situation where access to recovered volumes is temporarily removed upon a re-attempted recovery. In this release, volumes that have been successfully recovered will be skipped during re-attempts of recoveries.
4. ActiveCluster:
   1. During a stretched storage disaster recovery, the stretched volume is isolated at the target site, if prepareFailover failed.