Known issues
This section details the known issues in version 3.6.0, along with possible workarounds (if workarounds are available).
| Ticket ID | Description |
|---|---|
| VMSS-260691 | The direction of the GMCV replications shown in SRM will
sometimes display incorrectly if devices are manually discovered after a Recovery operation. This
issue only reproduces against GMCV. After a failover, the GMCV becomes idle, and SRM cannot detect the direction of the replication relationship. No other operations, such as Reprotect, however, are impacted. |
| SVCSRA-5161 | If the vCenter/SRM/ESX server is down while the IBM® storage is still working, the secondary recovery action might fail when the primary site is recovered. Workaround: Stop the remote copies with the access
option enabled on the storage system before running the secondary recovery.
|