Chiu
Sent: Friday, May 10, 2019 10:01 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: DR Failover
I need to check with our account manager again but this is my
understanding. We just replaced our DR mainframe with a Z14 ZR1. Part of
the acceptance testing was running our full DR suite at the DR site
I need to check with our account manager again but this is my
understanding. We just replaced our DR mainframe with a Z14 ZR1. Part of
the acceptance testing was running our full DR suite at the DR site. So we
activated a CBU which lasted 14 days I am told and ran our tests. The
purchase of the ne
We had worked out "In Theory" how we would do it.
About 18 months after we opened our second data center, Our Main Data Center
needed to shutdown over a long weekend, for 100% shutdown power maintenance.
After the Online's were shutdown Friday Night, We waited for all the DASD &
Tape to sync
d be
different . . . .
First Tennessee Bank
Mainframe Technical Support
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Jesse 1 Robinson
Sent: Tuesday, May 07, 2019 4:52 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: DR Failover
[External Email]
(Resurrecting an old th
Team Paddler
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-543-6132 Office ⇐=== NEW
robin...@sce.com
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of van
der Grijn, Bart (B)
Sent: Monday, June 5, 2017 5:07 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):
wallowed by the giant crater.
Bart
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Jesse 1 Robinson
Sent: Thursday, June 01, 2017 6:24 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: DR Failover
Never got traction on two of my quest
On Thu, 1 Jun 2017 19:18:06 -0400, Edward Finnell wrote:
>There were some really good user experiences on DR at SHARE.
One memorable comment from a DR experience presentation at SHARE
many years ago after (IIRC) a flood in Chicago took out a data center.
The presenter said that the reason thing
W dniu 2017-06-02 o 00:24, Jesse 1 Robinson pisze:
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?
Our company actually declared a disaster after a flood in 1993 when faced with
an extended power outage. We got to the hot site and began working on the
restore when a large enough truck mounted generator was obtained, so we didn't
actually have to go through with it. But it started me thinkin
cussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Tony Harminc
> Sent: Monday, May 29, 2017 6:10 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: (External):Re: DR Failover
>
> On 29 May 2017 at 11:02, Jesse 1 Robinson wrote:
>
> > So I'm wondering about other
@LISTSERV.UA.EDU] On
Behalf Of Edward Finnell
Sent: Thursday, June 1, 2017 4:18 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: EXTERNAL: Re: DR Failover
There were some really good user experiences on DR at SHARE. Think I was
most impressed with Ryder's plan. They even had it down to who was taking
There were some really good user experiences on DR at SHARE. Think I was
most impressed with Ryder's plan. They even had it down to who was taking
care of sysprog families while they were busy putting the company back
together.
Doesn't hurt to be inventive. When we had a big F4 Tornado come
st [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Jesse 1 Robinson
Sent: Thursday, June 1, 2017 3:24 PM
To: IBM-MAIN@LISTSERV.UA.EDU
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 actua
ernal):Re: DR Failover
On 29 May 2017 at 11:02, Jesse 1 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 yo
On 29 May 2017 at 11:02, Jesse 1 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 dat
On 30/05/2017 1:02 AM, Jesse 1 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 cente
Jesse Robinson wrote:
>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 outag
DU
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
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.
Jesse 1 Robinson wrote:
We have used the DR procedure twice in controlled settings to move production
from one data center to another, so we know it works
I wonder how many orgs have done this not-so-simple test.
--
Jack J. Woehr # Science is more than a body of knowledge. It's a way of
w
20 matches
Mail list logo
