Recovering primary site, h1 after reaching full-duplex state

Prepare to recover the primary site to allow the Multi-Target PPRC configuration to be restored.

1. Issue a failback command to the h2 to h1 volumes.

   TSO/E command	DS CLI command	ANTRQST API command	ICKDSF command
   CESTPAIR ACTION(FAILBACK)	failbackpprc	REQUEST=PESTPAIR ACTION=FAILBACK	PPRCOPY ESTPAIR FAILBACK

   The following actions occur after the PPRC failback command processes:

   • Out-of-sync data from h1 is merged with data on h2.
   • Updated status is sent to h1 and the following conditions apply:
     • Volume h1 changes to a PPRC secondary volume of h2.
     • Out-of-sync updates on volume h1 are discarded because h2 has the updated data.
     • A Multi-Target Incremental Resync pair to volume h3 is created.
   • Volumes h2 and h1 are resynchronized using out-of-sync updates recorded on volume h1.
2. Wait for the copy process of the h2 and h1 volumes to reach full-duplex status (all out-of-sync tracks have completed copying). You can monitor when the number of out-of-sync tracks reaches zero by querying the status of the volumes.

   TSO/E command	DS CLI command	ANTRQST API command	ICKDSF command
   CQUERY	lspprc -l	REQUEST=PQUERY	PPRCOPY QUERY

   After all data is copied, the h2 and h1 pair changes to a full-duplex state. The Multi-Target PPRC configuration is restored. Figure 1 shows production is running at h2, with Metro Mirror running between h1 and h3 volume pair.

   You can move production back to the primary site, h1 by using the steps in this scenario. However, if h1 and h2 are at the same location, it might not be required to move production back to h1.