Willy-nilly is about notification and opportunity for preparation. For example, management declares a surprise DR drill on a Saturday morning. So the techs execute their well-rehearsed swap-over plan and begin running production at the DR site. Real live transactions with actual customer data. The old production site is now obsolete.
Then Sunday at noon management decides to roll back before the new week starts off. There is no time to plan. No time to test. The entire environment has to copied back to prod overlaying the old data. And it has to work from the get-go. Can anyone step up to that challenge? If not there could be some serious willy damage. . . 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 Ed Jaffe Sent: Tuesday, February 12, 2019 4:04 PM To: [email protected] Subject: (External):Re: Wells Fargo? Well f*&%#d at the moment: Data center up in smoke, bank website, app down . The Register On 2/11/2019 7:06 PM, Jesse 1 Robinson wrote: > All of this bodes ill for willy-nilly switching back and forth between data > centers unless there's some secret trick(s) I don't know about. I don't know the tricks either. Guess I need to attend more DCM Project-sponsored sessions at SHARE... ;-) I can attest that we have a number of customers that swap workloads between two sites a couple/few times a year. (Does that count as willy/nilly?) We have one or two with a third site in the mix! Yikes!!! -- Phoenix Software International Edward E. Jaffe 831 Parkview Drive North El Segundo, CA 90245 https://www.phoenixsoftware.com/ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
