What happens to data that gets created/updated during the test? You say you 
resume production as if nothing had happened. But surely something did happen 
during those hours of testing. This is why we have assiduously avoided failover 
even during actual production outages: what happens to client data? During our 
regular tests, the DR environment is an 'island' where all applications are 
invited to test with throw-away data. At the end, the DR DASD farm is 
overwritten; all test data is lost. 

.
.
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 Elardus Engelbrecht
Sent: Monday, May 29, 2017 8:41 AM
To: [email protected]
Subject: (External):Re: DR Failover

Jesse Robinson 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?

We have no choice. We must have at least on/two formal tests per year for our 
z/OS systems. All LPARs are brought up at DR site. Network settings are changed 
everywhere (our networks, our clients networks and MF network).  All our 
clients are invited and they participate and report anything!

From the moment we declare a DR (and shut down everything at Primary Site), we 
are up and running at DR site in a few hours and users can continue with their 
work from their own offices. 

Since those DR tests are just tests, when the exercise is completed, we started 
up our Prod systems and continue as if nothing happened. We obtain feedback 
from everyone about everything under the sun, moon and stars...

Based on my recent posts ...

Everything (IPL procs, Network changes, etc.) is documented (.boo and .pdf 
formats as well as URLs placed too) and placed everywhere on laptops, shared 
network resources, hardcopies, external drives, etc. This is to enable external 
people to continue our work if all of us are dead or kaput. (Or simply 
disappear a la Crysis (game) via a remote tool. ;-D )

Based on complaints about KC, I must mention that we even test connections to 
big blue websites from DR site.

We (z/OS people) simply do not take any changes. 

Murphy and his laws are not welcome. ;-)

Groete / Greetings
Elardus Engelbrecht


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to