1) Our plan is documented in 2 parts. One for non Sysprog resources and one that contains the "sensitive" technical information. Our current plan requires technical level staff (Mid-level Sysprogs at a minimum). Recovery of the Mainframe systems is by System Programming staff only. (we do things like Flip the R1/R2 relationship in the DASD,Jes2 Checkpoint Reconfiguration, Some IP magic etc. as part of the recovery) We have no current plans to make our Recovery have an Easy Button for a Manager (even me !) to push. Renegotiation of staff contracts is always a possibility at that point in time <grin - only joking guys don't worry>
2) As our plans include a triage effect (run degraded during certain windows) for recovery and our applications are very tightly integrated with shared files /DB Tables we do not switch and run Production in the recovery site and recover back. In fact we document as part of the decision matrix for declaring a disaster that once declared there is a known window before we would be ready to fail back to the primary DC. All tests result in throw away data and we spend considerable efforts to ensure the separation of the DR systems while active from the Production users/Stores except for the chosen testers. Jerry Whitteridge Manager Mainframe Systems & Storage Albertsons - Safeway Inc. 623 869 5523 Corporate Tieline - 85523 If you feel in control you just aren't going fast enough. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Jesse 1 Robinson Sent: Thursday, June 1, 2017 3:24 PM To: [email protected] Subject: EXTERNAL: Re: DR Failover Never got traction on two of my questions, which are independent of technology. -- During a failover (test I would presume), who actually performs the DR procedure whatever it is? Sysprogs, operators, production control folks, or someone else? Has anyone dared to bring in a non-technical person like a manager? This question is crucial to business resiliency because, depending the reason for failover, your top technical folks may be indisposed for an extended duration. -- If you stayed in the DR environment long enough to have captured/updated live customer data, how did you eventually return to the production environment? This question is crucial to business resiliency because at some point down the line, you have to return or, as the poem goes, settle in for a long winter's nap. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Tony Harminc Sent: Monday, May 29, 2017 6:10 PM To: [email protected] Subject: (External):Re: DR Failover On 29 May 2017 at 11:02, Jesse 1 Robinson <[email protected]> wrote: > So I'm wondering about other shops' experience with mainframe DR. Has > it ever been necessary to keep the business running? Who orchestrated > the procedure? How long did it take? And finally, how did you get > production back to the primary data center? I have plenty of old war-stories from 1977 (heh - 40 years ago in Feb) when a fire forced us out of our building for a week. But most of those are barely relevant to today's world; not just that the technology has changed, but that we didn't *have* a DR plan, and relied on the good graces of IBM and (the then monopoly) Bell telecom to get us on the air temporarily. It was a lot of fun in its way, everyone learned a lot, and our ops manager dined well at SHARE and other places where he gave his fire slides talk for several years after. Certainly one now blindingly obvious thing we learned that hadn't really entered anyone's head at the time is that DR is at least as much a business and organizational problem as a technology one. For instance, in those days before mobile phones, and when the closest thing to email ran on the down mainframe, where do you *go* when your office building is surrounded by fire trucks and a lot of yellow tape and fast-freezing water, and there is no one to answer any of the work phones? Anyway - the old stories are probably more of a Friday topic than anything very useful in 2017. Tony H. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ________________________________ Warning: All e-mail sent to this address will be received by the corporate e-mail system, and is subject to archival and review by someone other than the recipient. This e-mail may contain proprietary information and is intended only for the use of the intended recipient(s). If the reader of this message is not the intended recipient(s), you are notified that you have received this message in error and that any review, dissemination, distribution or copying of this message is strictly prohibited. If you have received this message in error, please notify the sender immediately. ________________________________ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
