IBM DS6000 - Manual (Page 73)

Chapter 6. FlashCopy overview 49
occurred on the source or on the target will stay as they were at the time when the FlashCopy
was established.
If the
persistent
FlashCopy option was specified, the FlashCopy relationship must be
withdrawn explicitly.
6.4 FlashCopy in combination with other Copy Services
Volume-based FlashCopy can be used in various combinations with other Copy Services,
whereas the most suitable will depend on the characteristics of the environment and the
requirements.
6.4.1 FlashCopy and Metro Mirror
Figure 6-7 FlashCopy and Metro Mirror
As illustrated in Figure 6-7, the following combinations are supported at the primary Metro
Mirror site:
A FlashCopy
source volume
can become a Metro Mirror
primary volume
and vice versa.
The order of creation is optional.
A FlashCopy
target volume
can become a Metro Mirror
primary volume
and vice versa. If
you wish to use a FlashCopy target volume as a Metro Mirror primary, be aware of the
following considerations:
– The recommended order is to first establish the Metro Mirror, and then create a
FlashCopy to that Metro Mirror primary using the -tgtpprc parameter if using DS CLI,
or TGTPPRIM(YES) if using TSO, or PPRCPRIM(YES) if using ICKDSF, or
FCTOPPRCPrimary if using DFSMSdss.
The Metro Mirror secondary will not be in a fully consistent state until the Metro Mirror
enters the full duplex state.
Note: The scenarios discussed in the present section do not apply to data set FlashCopy.
source target
FlashCopy
Metro
Mirror
primary
secondary primary
Metro
Mirror
source target
FlashCopy