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

In this case, either use FORCEFLAG to startup the package on SVOL site or fix the problem and
resume the data replication with the following procedures:
1. Split the device group pair completely (pairsplit -g <dg> -S).
2. Re-create a pair from original PVOL as source (use paircreate command).
3. Startup package on either the PVOL site or SVOL site.
Takeover timeout for Continuous Access journal mode
A takeover timeout occurs when a package failover to the secondary site (SVOL) and Metrocluster
Continuous Access issues takeover (either swap or SVOL takeover) command on SVOL. If the
journal group pair is flushing the journal data from PVOL to SVOL and takeover timeout occurs,
the package does not start and the following situations occur:
• The device group pair state remains in PVOL-PAIR/SVOL-PAIR.
• The journal data is being transferred to the SVOL.
In this case, it is required to wait for the completion of the journal data flushing and the state for
every of the following:
• Primary site: PVOL-PAIR or PVOL-PSUS(E)
• Secondary site: SVOL-PSUS(SSWS) or SVOL-PSUE(SSWS)
At this point, use the FORCEFLAG to startup the package on SVOL site or (2) to fix the problem (if
any of Continuous Access links was failed) and resume the data replication with the following
procedures:
1. Split the device group pair completely (pairsplit -g <dg> -S).
2. Re-create a pair from original PVOL as source (use the paircreate command).
3. Startup package on PVOL site (or SVOL site).
PVOL-PAIR with SVOL-PSUS(SSWS) state for Continuous Access journal mode
PVOL-PAIR with SVOL-PSUS(SSWS) is an intermediate state. The following is one scenario that
leads to this state:
• At T1, device pair is in PVOL-PAIR/SVOL-PAIR and the AP value is 0 in SVOL site. In other
words, all Continuous Access links fail.
• At T2, package failovers from PVOL site to SVOL site. The Metrocluster Continuous Access
issues SVOL-Takeover at the SVOL site and the state will become SVOL-PSUS(SSWS) and
PVOL-PAIR.
• At T3, all Continuous Access links have been recovered. The state stays in SVOL-PSUS (SSWS)
and PVOL-PAIR. The duration the PVOL remains in PAIR state is relatively short
The PVOL-PAIR/SVOL-PSUS (SSWS) is an invalid state for P9000 or XP Asynchronous (both
Continuous Access/Asynchronous and Continuous Access Journal). In this state, by running the
pairresync or takeover command, will fail. It is necessary to wait for the PVOL to become
PSUE.
Administering the SADTA configuration
This section elaborates the procedures that must be followed to administer a SADTA configuration
in which complex workloads other than Oracle RAC are configured.
Maintaining a node
To perform maintenance procedures on a cluster node, the node must be removed from the cluster.
Run the cmhaltnode -f command to move the node out of the cluster. This command halts the
complex workload package instance running on the node. As long as there are other nodes in the
site and the Site Controller Package is still running on the site, the site aware disaster tolerant
workload continues to run with one less instance on the same site.
74 Administering Metrocluster