I'm sure that GDPS can do more than what we use it for. We mirror and recover parallel sysplexes as well between data centers. Even if I had only monoplexes mission critical to my business, I would still use DASD mirroring (XRC or whatever) and recover at a 'cool' site via GDPS, which handles DASD and CECs alike. In my view, what's truly crucial to a business is data. I need to IPL a system to resume business with data intact. If a few hours elapse, so be it. Compare that with the ancient goal (wish) of restoring data from tape. Hopeless.
The thought of running a parallel sysplex across data centers 100+ KM apart gives me the freaking heebie-jeebies. Even if my communication (DWDM) were absolutely 100% reliable, where would my data actually live? Volume ABC123 lives at one data center or the other. If the owning data center fails, my sysplex is toast. If I mirror ABC123, I can only update one copy or the other. I can't update both or I'll screw the 'other' guy. Maybe there are technical answers that I don't understand. I stand to be educated. . . . 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 Rob Schramm Sent: Thursday, May 28, 2015 11:28 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: LPAR MOBILITY But GDPS is not just a Disaster Recovery solution. It can "live" swap from data center to data center, within data centers. Are you saying that you are just a base sysplex using GDPS? Rob Schramm On Thu, May 28, 2015 at 1:55 PM J O Skip Robinson <jo.skip.robin...@sce.com> wrote: > GDPS has about as much to do with 'parallel sysplex' as TSO has to do > with 'time sharing'. For us, GDPS automates disaster recovery. Before > GDPS, we had to do a lot of manual procedures that GDPS performs > without the need for fingers on a keyboard. Included in our DR > environment is one monoplex LPAR that runs TPX. This LPAR has no need > for sysplex resources but has to run in DR, which we view as business > resumption after a catastrophic data center failure. RTO is important, > but a few hours is far preferable to the alternative abyss. > > . > . > . > 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 Rob Schramm > Sent: Thursday, May 28, 2015 6:21 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: LPAR MOBILITY > > Interesting, never thought someone would consider GDPS on anything but > parallel sysplex. What would be the point? I could buy a Ferrari and > remove the wheels.. But it wouldn't be much fun...and would be a very > expensive chair. > > Seems more like the person is looking for parallel sysplex / > sysplex-in-a-box plus automation. > > Rob Schramm > > On Thu, May 28, 2015, 9:01 AM IBMZOS < > 000000af65f10fb1-dmarc-requ...@listserv.ua.edu> wrote: > > > Thank's Jan for detailed reply. Yes for the impact of LPM. We use it > > for planned outages, and work fine. I cannot do with my sysplex, > > because your reply is applicable to a Parallel sysplex, which is a > > HIGH > step forward. > > From all the reply, i understand that Parallel Syplex is really the > > solution. Just curious if LPM or Live Guest Migration is announced > > one day on Z/OS, for planned outages... ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
