SAN Volume Controller and Storwize family systems running V6.3, V6.4 or V7.1 may experience undetected data loss on a secondary volume in a Global Mirror with Change Volumes relationship if a non-Change Volume FlashCopy map of the primary volume exists.
This issue is exposed when using Global Mirror with Change Volumes (GMCV) and FlashCopy on the same primary volume.
A system will be exposed to this issue if a separate non-Change Volume FlashCopy map exists where the FlashCopy source volume is also the primary volume in a GMCV relationship.
If the FlashCopy map is started while the GMCV relationship is actively replicating data to a secondary volume and the GMCV relationship completes its active cycle before the FlashCopy has stopped, the secondary volume data will not be updated with all primary volume changes and this will constitute an undetected data loss on the secondary volume.
Customers with systems using this configuration are advised to check the consistency of the data on their GMCV secondary volumes.
This issue can be prevented by either ensuring that FlashCopy maps are not started when associated GMCV relationships are active, or by refraining from using GMCV primary volumes in separate FlashCopy maps.
This issue was resolved by APAR IC94405 in the V188.8.131.52 PTF and V184.108.40.206 PTF and higher releases.
This issue was also resolved in IBM Storwize V7000 Unified File Module 220.127.116.11 and higher releases.
|Storage Virtualization||SAN Volume Controller||7.1||SAN Volume Controller||6.3, 6.4, 7.1|
|Disk Storage Systems||IBM Storwize V7000 Unified (2073)||IBM Storwize V7000||1.3, 1.4|
|Disk Storage Systems||IBM Storwize V3700 (2072)||7.1||Platform Independent||6.4, 7.1|