Role of data mirroring in recovery from a rolling disaster
In a real disaster, your local site gradually and intermittently fails for a duration of several seconds. This kind of Db2 failure is known as a rolling disaster. You can recover from a rolling disaster by using data mirroring.
To use data mirroring for disaster recovery, you must mirror data from your local site with a method that does not reproduce a rolling disaster at your recovery site. To recover a Db2 subsystem and data with data integrity, you must use volumes that end at a consistent point in time for each Db2 subsystem or data sharing group. Mirroring a rolling disaster causes volumes at your recovery site to end over a span of time rather than at one single point.
The following figure shows how a rolling disaster can cause data to become inconsistent between two subsystems.

- Some time prior to 12:00: A table space is updated in the buffer pool.
- 12:00 The log record is written to disk on logical storage subsystem 1.
- 12:01: Logical storage subsystem 2 fails.
- 12:02: The update to the table space is externalized to logical storage subsystem 2 but is not written because subsystem 2 failed.
- 12:03: The log record that indicates that the table space update was made is written to disk on logical storage subsystem 1.
- 12:03: Logical storage subsystem 1 fails.
Because the logical storage subsystems do not fail at the same point in time, they contain inconsistent data. In this scenario, the log indicates that the update is applied to the table space, but the update is not applied to the data volume that holds this table space.