Jesse, Round trip delay time is the same on ESCON and Fiber Channel, but the mother-may-I nature of ESCON protocols used to pump-up the droop factor, even at 10km. Fiber Channel links changed the viability of synchronous at metro distances substantially.
Personally, I think that the myth of zero data loss is not worth the performance impact when compared to asynchronous methods. By the time in-flight transactions have been rolled back the delta between application recovery times with synchronous and asynchronous is often 3/5 of 5/8 of a poofteenth. Next time you refresh your storage, you may want to look at other asynchronous remote copy technology, as XRC is not necessarily the best option anymore (he says with a skewed POV). Ron -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Jesse 1 Robinson Sent: Thursday, June 7, 2018 11:22 AM To: [email protected] Subject: Re: [IBM-MAIN] PPRC-XD vs Async PPRC Data consistency was one of two reasons we chose circa 2000 to use XRC rather than PPRC. I know the technology has changed, and I've been *told* that PPRC is now capable of maintaining consistency, but I have not seen it in action. The other reason for XRC BTW was the synchronizing problem: we could not tolerate the I/O delay waiting for remote confirmation from 120 KM via ESCON. In 2000, everything was slower. Now we use DWDM via FICON. . . 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 R.S. Sent: Thursday, June 07, 2018 4:10 AM To: [email protected] Subject: (External):Re: PPRC-XD vs Async PPRC W dniu 2018-06-06 o 18:18, Sankaranarayanan, Vignesh pisze: > Hello All, > > Please could you point me to any doc explaining the differences between the 2. > Any important, obscure, techdocs or KB page or some such as well.. ? Fundamental difference is data consistency. PPRC-XD is *inconsistent* copy during most of the time. Inconsistent is unusable. You have to quiesce the production and wait a little until the delta become zero (the copy become consistent). Asynchronous copy like XRC, SRDF/A, HARC is different. It is *consistent* copy - data on secondary site is usable, but is not current. Of course the time delta is small, but the most important is you don't have later data while earlier data is missing. -- Radoslaw Skorupka Lodz, Poland ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
