I recently thought I had sent this question to the list but nobody replied and even my message didn't appear in the list.
At the risk of spamming the list I thought I would try again since it seems there must be folks on the list who are using Metro Mirror and have made conscious decisions about freeze/stop and freeze/go Thanks On Sat, Jul 9, 2022 at 2:27 PM Laurence Chiu <lch...@gmail.com> wrote: > Slowly moving to a full test of a site swap after a successful HyperSwap > exercise. > > Our outsourcers had set Copy Services Manager to choose Freeze/Go versus > Freeze/Stop in the event of a PPRC failure. This is apparently the most > common setting for sites that use Metro Mirror since it's likely the PPRC > failure is due to some sort of comms failure and why stop production > workload when the comms load can be possibly fixed relatively quickly. > > Of course it does mean your DR site is out of sync and if you do lose your > primary site while the rolling disaster is underway, then you could lose > data. > > Discussions with colleagues and we think perhaps if there is a Metro > Mirror failure and we can't of course HyperSwap, we should evaluate the > potential outage time and if appropriate do a site swap to reduce risk of > data loss. > > Just wondering what others do. > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN