I remain impressed with Jerry's accomplishment. Our outage was on the order of 12 hours, but that included time for major network configuration changes and for hours of user testing. They had to give thumbs up for staying in the new location. Until the move was declared successful, we could not allow any actual production work, which would have updated data in a (possibly) throw-away location. There was no going back.
. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile jo.skip.robin...@sce.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jerry Whitteridge Sent: Tuesday, November 17, 2015 2:56 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Moving a Sysplex Mark If you look at the Share presentations in Seattle I presented on moving a Datacenter (2 sysplexes ) and how we did it. If you look at that I'd be happy to discuss any questions that arise. My windows were only the time it took for replication to go consistent and then the times to IPL and verify. Jerry Whitteridge Manager Mainframe Systems & Storage Albertsons - Safeway Inc. 925 738 9443 Corporate Tieline - 89443 If you feel in control you just aren't going fast enough. -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Mark Jacobs - Listserv Sent: Tuesday, November 17, 2015 2:51 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Moving a Sysplex Thanks for the information. Do you remember how long your outage was? We're being told (using one solution) that the outage will be on the order of two hours. Mark Jacobs > J O Skip Robinson <mailto:jo.skip.robin...@sce.com> November 17, 2015 > at 2:11 PM Others may know something I don't, but I would answer No. I > don't believe you can run a (parallel) sysplex over that distance > because of CF link limitations. Furthermore, assuming that you could > somehow get one sysplex member sharing across that distance, you would > have to switch from using production DASD volumes to GDPS-mirrored > volumes. I just don't see how you could do that seamlessly. We > performed a multi-sysplex move a couple of years back using > essentially GDPS DR procedures, but we took a full outage to > accomplish it. > > . > . > . > J.O.Skip Robinson > Southern California Edison Company > Electric Dragon Team Paddler > SHARE MVS Program Co-Manager > 626-302-7535 Office > 323-715-0595 Mobile > jo.skip.robin...@sce.com > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Mark Jacobs - Listserv > Sent: Tuesday, November 17, 2015 11:02 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: (External):Moving a Sysplex > > Would a GDPS like solution work for moving a sysplex from here to > there, where the there is over 1200 miles from here, without taking a > sysplex outage? > -- > Mark Jacobs > Time Customer Service > Technology and Product Engineering > > The standard you walk past, is the standard you accept. > Lieutenant General David Morrison > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > Please be alert for any emails that may ask you for login information > or directs you to login via a link. If you believe this message is a > phish or aren't sure whether this message is trustworthy, please send > the original message as an attachment to 'phish...@timeinc.com'. > -- Mark Jacobs Time Customer Service Technology and Product Engineering The standard you walk past is the standard you accept. Lt. Gen. David Morrison ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
