Setting up a two Metro Mirror pair configuration

Use this scenario to set up a two Metro Mirror pair configuration.

1. Create PPRC paths between all related volumes, including between any future secondary volumes to prepare for future recovery scenarios.
   It is not required that all paths be established initially and in both directions, but it is recommended to help simplify the recovery procedures. For example, create paths using the following examples and as shown in Figure 1.

   • h1 to h2
   • h1 to h3
   • h2 to h1
   • h2 to h3
   • h3 to h1
   • h3 to h2

   TSO/E	DS CLI	ANTRQST API	ICKDSF
   TSO CESTPATH	mkpprcpath	REQUEST=PESTPATH	PPRCOPY ESTPATH

   

2. Create the first h1 and h2 Metro Mirror volume pair.

   You can create a Global Copy relationship between the pair (either by using TPC-R and GDPS®) or directly in a Metro Mirror relationship. Figure 2 shows the first Metro Mirror volume pair that is created. If you initially created the volume pair in a Global Copy relationship, you can use a subsequent PPRC Establish command to convert the pair to a Metro Mirror relationship.

   TSO/E	DS CLI	ANTRQST API	ICKDSF
   TSO CESTPAIR	mkpprc	REQUEST=PESTPAIR	PPRCOPY ESTPAIR

   

3. Create the second h1 and h3 Metro Mirror volume pair.
   You can complete steps 2 and 3 in any order. The two relationships are equal. Similar to the initial volume pair, you can create a Global Copy relationship between this pair initially or directly as Metro Mirror. Figure 3 shows the second Metro Mirror volume pair that is created.

   Note: If microcode on all storage systems does not support Multi-Target PPRC, the command is rejected.

   When you create the h1 and h3 volume pair, primary h1 detects the creation of a Multi-Target PPRC configuration. As part of the command processing, volume h3 becomes a secondary to volume h1 and volume h3 becomes a partner volume to volume h2. When volume h3 receives the partner information, it creates a Multi-Target Incremental Resync pair to volume h2.

   Primary h1 sends information to h2 with partner information describing h3 and h2 and then creates a Multi-Target Incremental Resync pair to h3.