IBMGlobalMirrorDataIntegrityFLASH.doc

IBM Global Mirror Data Integrity FLASH Procedure to Resynchronize the Primary and Secondary Volumes of Global Mirror Relationships Version 1.0 March 20, 2015 Document revisions: Revision Updated by Changes 1st – March 20, 2015 William F Wiegand wiegandb@ Initial version of the document.  Overview Global Mirror Flash Link: /support/docview.wss?uid=ssg1S1005053 Global Mirror Source Data May Be Incompletely Replicated to Target Volumes Flash (Alert) Abstract Systems utilizing Global Mirror running V7.2.0 or V7.3.0 releases earlier than V1 or V may experience an undetected inconsistency of data between source and target volumes. Content In Global Mirror environments in which the secondary SVC cluster or Storwize system is running or has previously run a V7.2.0 or V7.3.0 release earlier than V1 or V, there is a potential for source volume data to have been incompletely replicated to target volumes. This will remain undetected by the SVC or Storwize system. This issue can be caused by a number of conditions, which may include the issuing of Global Mirror commands and/or communication issues that may be present between primary and secondary clusters such as dropped fibre channel frames. The range and timings of these conditions are such that it is not possible to define predictable trigger mechanisms in order to implement a preventative workaround. This issue does not affect Global Mirror with Change Volumes. Fix This issue was resolved by APAR HU00658 in V1, V and V. In order to upgrade directly to V7.4.0 from affected releases, all active Global Mirror relationships must be in the Stopped state, and can be safely restarted once the upgrade has completed. This upgrade restriction is expected to be lifted in a future V7.4.0 PTF release. Note that any secondary systems that have previously run affected levels, even if they are no longer running these levels, may have caused target volume data inconsistencies in the past, so should be verified