HP XP P9500 Storage - Manual (Page 69)

(for example, database log files). These S-VOLs should be recovered using files that you have
confirmed to be current.
3. Perform file recovery as needed.
4. At the secondary site, connect to each remote system and release all Continuous Access
Synchronous pairs.
When an S-VOL changes to simplex, you cannot distinguish it from a non-Continuous Access
Synchronous simplex volume. If necessary, use the volume manager to change the volume
labels of the S-VOLs.
5. Complete file recovery procedures.
6. When file recovery procedures have been completed, vary the S-VOLs online.
7. At the secondary site, start critical host operations, with the previous S-VOLs now the primary
volumes.
Analyze S-VOL currency
The following helps you determine an S-VOL’s currency based on pair status and P-VOL fence level
setting.
Table 28 Analyzing S-VOL currency
Currency of S-VOL Fence level Case S-VOL status
Inconsistent. This S-VOL does not belong to a Continuous Access
Synchronous pair. Even if you established a Continuous Access Data Status
Never -- SMPL
Synchronous pair for this volume, you must regard this volume
as inconsistent.
Inconsistent. This S-VOL is not synchronized because not all tracks
have been copied from the P-VOL yet. This S-VOL must be
initialized (or copied from the P-VOL at a later time). Data Status
Never -- COPY
Current. This S-VOL is synchronized with its P-VOL. Data Status -- PAIR
* Needs to be analyzed. This S-VOL requires further analysis to
determine its level of currency. Never
Inconsistent. This S-VOL is not synchronized because not all tracks
have been copied from the P-VOL yet. This S-VOL must be
initialized (or copied from the P-VOL at a later time). Data Status
Never Initial copy
failed PSUE
Suspect. This S-VOL is not synchronized with its P-VOL if any write
I/Os were issued to the P-VOL after the pair was split. This pair Data Status
Never P-VOL by
operator PSUS
should be released and restarted using Entire Volume for Initial
Copy option. If you are sure that no data on the P-VOL changed,
you can use the None option.
Current. This S-VOL is synchronized with its P-VOL. Data All other types PSUS or PSUE
Suspect. This S-VOL is not synchronized with its P-VOL if any write
I/Os were issued to the P-VOL after the pair was split. Restore Status Never
the consistency of this S-VOL and update it, if required. The time
of suspension indicated on the Last Update Time field of the
Detailed Information dialog box (MCU SVP time) will help to
determine the last time this S-VOL was updated.
* For pairs with a P-VOL fence level setting of Never, further analysis is required to determine the S-VOL currency. This
can be determined by using sense information transferred via host failover, or by comparing the contents of the S-VOL
with other files that are confirmed to be current (for example, database log files). The S-VOLs should be recovered
using the files that are confirmed to be current.
Actual data recovery must be done using recovery point data in the database redo log.
Switch operations to the secondary site 69