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.

a.Check the pair status of the dg12 device group.

#pairvolchk -g dg12 -s

b.If the local dg12 volume is in PVOL or SVOL-SSWS

#pairsplit -g dg12

Go to Step 2

If the local dg volume is other than SVOL-SSWS or PVOL perform an SVOL takeover to make the local volume SVOL-SSWS or PVOL.

#horctakeover -g dg12 -S

#pairsplit -g dg12

Go to step 2,

If above command fails, split the pair to SMPL.

#pairsplit -g dg12 -S

2.Resync data from DC3 to DC1.

Resync the Journal device group to get the latest data from DC3 to DC1.

a.Check the pair status of dg13 at DC3.

#pairvolchk -g dg13 -s -c

b.If dg13 (DC3 side) is in PVOL

#pairresync -g dg13

Or

If dg13 (DC3 side) is in SVOL-SSWS.

#pairresync -g dg13 -c 15 -swapp

c. Wait for the PAIR state to come up for the Journal device group.

#pairevtwait -g dg13 -t 300 -s pair

Failback Scenarios 469