Sure appreciate everyone's input...thanks! I probably should have added a little more info upfront. Currently, we have primary, secondary, and tertiary volumes. We run off the tertiary volumes after flashing from the secondary' and clipping off the primary's. This works great for running a DR test and if we ever had a real "smoking hole" disaster but what we are trying to account for now is if we have a short outage(a few weeks) due to chemical spill, power outage etc. where we would have to come back to site A at some point.
Andrew, I have a few questions: 1) Do you know why a full XRC re-sync is avoided if you put the pairs into the mirror before bringing up your recovery LPAR? I'm struggling to wrap my brain around this because reversing the mirror before or after bringing up the recovery LPAR would still require using new SDMs and using new state, control and journal datasets at site A 2) Are you running GDPS? 3) Do you have site A tertiary volumes or just site B? 4) With our current environment we would reverse replicate from tertiary volumes back to the old primary's in site A. XRC is paired using volsers so to create the new pairings coming back would we have to run something like an FDReport for our new primary's and clip the old primary's to something like TTucb? How do you create your new pairings? 5) When done running production in site B and ready to come back, would you simply drop the SDMs, vary tertiary offline while leaving the old primary's you were replicating to online and issue an XRecover to clip them from the tertiary? Thanks -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Andrew Metcalfe Sent: Friday, June 07, 2013 2:24 AM To: [email protected] Subject: Re: XRC Volume Resync on a Return Home When we perform a "region switch" we reverse XRC replication before bringing up the production systems. Essentially as follows (some sequences shortened/omitted!) Shut down Region A production systems Shut down SDM in Region B Start SDM system in Region A looking at Region B dasd Load production systems in Region A If you fail to reverse XRC prior to the load of the systems in Region B, you are looking at a full XRC re-sync of Region B to Region A with no (usable) DR position until full duplex is established. Regards Andrew Metcalfe -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Mike Schwab Sent: 07 June 2013 05:24 To: [email protected] Subject: Re: XRC Volume Resync on a Return Home Actually, once Site A was down and Site B was Production, you should have established mirroring from Site B to Site A in case a problem happened at Site B and you needed to resume at Site A with the data from Site B. On Thu, Jun 6, 2013 at 8:08 PM, Skip Robinson <[email protected]> wrote: > OK, I really did not understand the process. Site A mirrors to Site B. > True production runs at Site B for some time. Then you want to mirror > back to Site A with then current data resulting from ongoing > production at Site B. > > The answer is that you must entirely mirror *all* data from Site B > back to Site A in order to get up to date. It's not just a matter of > reversing direction. It's how XRC works (and I suspect also PPRC > although I have no experience with it). -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN This e-mail and any attachments are confidential and intended solely for the addressee and may also be privileged or exempt from disclosure under applicable law. If you are not the addressee, or have received this e-mail in error, please notify the sender immediately, delete it from your system and do not copy, disclose or otherwise act upon any part of this e-mail or its attachments. Internet communications are not guaranteed to be secure or virus-free. The Barclays Group does not accept responsibility for any loss arising from unauthorised access to, or interference with, any Internet communications by any third party, or from the transmission of any viruses. Replies to this e-mail may be monitored by the Barclays Group for operational or business reasons. Any opinion or other information in this e-mail or its attachments that does not relate to the business of the Barclays Group is personal to the sender and is not given or endorsed by the Barclays Group. Barclays Bank PLC. Registered in England and Wales (registered no. 1026167). Registered Office: 1 Churchill Place, London, E14 5HP, United Kingdom. Barclays Bank PLC is authorised by the Prudential Regulation Authority and regulated by the Financial Conduct Authority and the Prudential Regulation Authority (Financial Services Register No. 122702). ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
