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

3. Resync sync device group to get latest data from DC2 to DC1.
Log onto any node at DC2.
• If in Step 1, the dg12 pair has been brought to SMPL state.
a. Create the DC1 and DC2 Sync device group when using 3DC Sync/CAJ replication.
# paircreate -g dg12 -f never/data -c 15 –vl
Or
Create the DC1 and DC2 Journal device group when using 3DC CAJ/CAJ replication.
# paircreate -g dg12 -f async -c 15 –vl –jp <journal id> -js
<journalid>
b. Wait for the PAIR state to come up for the DG12 device group.
# pairevtwait -g dg12 -t 300 -s pair
Go to Step 4
• If in Step 1, the dg12 pair was not split to SMPL and the dg12 local volume is PVOL.
If dg12 (DC1 side) is in SVOL-SSWS.
# pairsplit -g dg12 -RB
a.
# pairsplit -g dg12
b. Resync the device group dg12
# pairresync -g dg12
c. Wait for the dg12 device group to attain the PAIR state.
# pairevtwait -g dg12 -t 300 -s pair
Go to Step 4
• If in Step 1 the dg12 pair was not split to SMPL and dg12 local volume is SVOL-SSWS.
a. Resync the device group to make local volume PVOL.
# pairresync -g dg12 -c 15 -swaps
b. Wait for the dg12 device group to attain the PAIR state.
# pairevtwait -g dg12 -t 300 -s pair
4. Log on and perform the following from any DC1 node.
a. SWAP the roles of the dg12 device group between DC1 and DC2.
# horctakeover -g dg12 -t 360
5. Log on and perform the following from any DC2 node:
a. Wait for PSUS to come up for the Journal Device Group, dg23.
# pairevtwait -g dg23 -t 300 -s psus
b. Resync the Journal device group.
# pairresync -g dg23
c. Wait for the PAIR state to come up for the Journal device group.
# pairevtwait -g dg23 -t 300 -s pair
MULTI-TARGET-BI-LINK Data Recovery from DC3 to DC1
Use the following steps to restart a package back to DC1 after the package fails over to DC3:
1. Log on to any node on DC1.
Failback Scenarios 147