IBM Support

HIPER: Undetected data corruption when using policy-based high availability after certain support-assisted disaster recovery procedures are performed.

Flashes (Alerts)


Abstract

After certain support-assisted disaster recovery procedures, volumes may be accessible for host I/O on both HA systems, even though replication is not active. This can result in undetected data corruption, because the data is not synchronized between the two copies.

Systems using HyperSwap or stretched cluster for high availability are not affected

Content

When using policy-based high availability (PBHA), there are two connected IBM Storage Virtualize systems (FlashSystem or SAN Volume Controller), and both of those systems present paths to the same volume to the same hosts.    The Storage Virtualize replication software is used to keep the data on the two copies in sync at all times.
Under rare circumstances one of the two Storage Virtualize systems may need to be restored from an internally maintained configuration back up.  This recovery is known as a Tier 3 recovery procedure, and should only be performed under guidance from IBM support.
If the PBHA Storage Virtualize system is running 8.6.1.0 or later , there is a possibility that after performing a T3 recovery, a host may be able to access a volume on both Storage Virtualize systems, even though even though high availability is not established.  This situation can result in undetected data corruption, because the writes are not synchronized between the two copies.
This issue is resolved under APAR SVAPAR-156849 in 8.7.0.4 and 8.7.3.1
Systems using policy-based high availability are recommended to update to 8.7.0.4 or later, which also includes fixes for additional APARs for high availability as listed in the release note.

[{"Type":"MASTER","Line of Business":{"code":"LOB26","label":"Storage"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSRFRYE","label":"IBM FlashSystem 9500"},"ARM Category":[{"code":"a8m0z000000bqQAAAY","label":"Code (Code\/Drive firmware\/IFix)"}],"Platform":[{"code":"PF025","label":"Platform Independent"}]},{"Type":"MASTER","Line of Business":{"code":"LOB66","label":"Technology Lifecycle Services"},"Business Unit":{"code":"BU070","label":"IBM Infrastructure"},"Product":{"code":"SSM2RC","label":"FLASHSYSTEM 5300"},"ARM Category":[{"code":"a8m0z000000bqQAAAY","label":"Code (Code\/Drive firmware\/IFix)"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"},{"Type":"MASTER","Line of Business":{"code":"LOB26","label":"Storage"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSJPVJ","label":"IBM FlashSystem 5200"},"ARM Category":[{"code":"a8m0z000000bqQAAAY","label":"Code (Code\/Drive firmware\/IFix)"}],"Platform":[{"code":"PF025","label":"Platform Independent"}]},{"Type":"MASTER","Line of Business":{"code":"LOB26","label":"Storage"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSV1DQD","label":"IBM FlashSystem 7300"},"ARM Category":[{"code":"a8m0z000000bqQAAAY","label":"Code (Code\/Drive firmware\/IFix)"}],"Platform":[{"code":"PF025","label":"Platform Independent"}]},{"Type":"MASTER","Line of Business":{"code":"LOB26","label":"Storage"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"ST3FR3","label":"IBM FlashSystem 7200"},"ARM Category":[{"code":"a8m0z000000bqQAAAY","label":"Code (Code\/Drive firmware\/IFix)"}],"Platform":[{"code":"PF025","label":"Platform Independent"}]},{"Type":"MASTER","Line of Business":{"code":"LOB26","label":"Storage"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"ST3FR9","label":"IBM FlashSystem 5x00"},"ARM Category":[{"code":"a8m0z000000bqQAAAY","label":"Code (Code\/Drive firmware\/IFix)"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]

Document Information

Modified date:
15 May 2025

UID

ibm17231619