Building Disaster Recovery Serviceguard Solutions Using Metrocluster with Continuous Access for P9000 and XP A.11.00

1. The device group pair state remains in PVOL-PAIR/SVOL-PAIR
2. The journal data continues transferring to the SVOL
In this case, you must wait for the completion of the journal data flushing and the Continuous
Access-Journal pair state to be:
• Hot-standby site: PVOL-PAIR or PVOL-PSUS(E)
• Third site: SVOL-PSUS(SSWS) or SVOL-PSUE(SSWS)
Either 1) use FORCEFLAG to startup the package on third site or 2) fix the problem (if any of
Continuous Access links was failed) and resume the data replication with the following procedures:
1. Split the Continuous Access-Journal device group pair completely (pairsplit -g <dg>-S>
2. Re-create a Continuous Access-Journal pair from it’s original PVOL as source. (use the
paircreate command)
NOTE: You can specify “none” as the copy mode for initial copy operations. If the none mode
is selected, full copy operations are not performed. The user is responsible for using the none mode
only when the user is sure that data in the primary data volume is exactly the same as data in the
secondary data volume.
Continuous Access-Journal Device Group PVOL-PAIR with SVOL-PSUS(SSWS) State
PVOL-PAIR with SVOL-PSUS(SSWS)is an intermediate state. It could happen, but is unlikely to be
seen. The state PVOL-PAIR/SVOL-SSWS is an invalid state for P9000 or XP Continuous Access
Journal. In this state, if you issue a pairresync or takeover command, it would fail. It is necessary
to wait for the PVOL to become PSUE or PSUS.
Data Maintenance with the Failure of a Metrocluster with Continuous Access for P9000 and XP Failover 153