#pairsplit -g dg12

d.If the above command fails, then split the pair to SMPL state.

#pairsplit -g dg12 –S

2.Resync data from DC3 to DC2.

Log onto any node at DC2. Resync Journal device group to get the latest data from DC3 to DC2.

a.Check the pair status of dg23 (DC3 side).

#pairvolchk -g dg23 -s -c

b.If dg23 (DC3 side) is in PVOL.

#pairresync -g dg23

Or

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

#pairresync -g dg23 -c 15 -swapp

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

#pairevtwait -g dg23 -t 300 -s pair

d.Swap the role of Journal device group between DC2 and DC3

#horctakeover -g dg23 -t 360

e.Wait for the Journal device group to attain the PAIR state.

#pairevtwait -g dg23 -t 300 -s pair

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.

a.If dg12 (DC1 side) is in SVOL-SSWS.

#pairsplit -g dg12 -RB

#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.

468 Designing a Three Data Center Disaster Recovery Solution