We currently have a MTMGM (Multi-target, Metro Global Mirror)
implementation. Most of our volumes are in this MTMGM configuration,
however we have a few that are not. We have a volume, say at address
A000, that is not part of the MTMGM nor part of any other copyset. We
have a batch job that copies to this A000 address using
FASTREPLICATION(PREFERRED), so it uses flashcopy and the job completes
very quickly. Back in 2019, we decided to add this A000 volume to a
metro mirror copyset. When the batch job ran, it couldn't use
flashcopy and fell back to standard data movement. This extended our
batch window and is not acceptable. I don't remember exactly what the
error was but vaguely recall it was something about not being able to
use FC to a target when that target was also a PPRC source.
Has anything changed with regard to using FC to a volume that is part of
the MTMGM or any other copyset?
MTMGM: Our config is we have one DS8950 as our primary DASD box, we
have another DS8950 being used as a Metro Mirror box colocated with the
primary and we have a third DS8886 (soon to be a new DS8950) box at a
remote site using Global Mirror. We use MTMGM to replicate from the
primary to the MM box and using GM to the remote box.
We really want to add the other volumes to the MTMGM but don't want to
affect the batch Flashcopies to those other volumes. Clear as mud?
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
