OK, I guess I didn't realize that there was some mirroring software that didn't allow a changed-only resync after updates were done on the target volumes.
Rex -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Mike Schwab Sent: Tuesday, February 14, 2012 4:10 PM To: [email protected] Subject: Re: Changing sysplex hardware Resync after the secondary volume is updated? If the mirroring software supports that, it would save a lot of retransmitting. I am fairly sure the ESS F20 and 800 PPRC did not have that, and the user did not say what he is using to mirror. But you only need that after a backout after running at the new site. On Tue, Feb 14, 2012 at 3:54 PM, Pommier, Rex R. <[email protected]> wrote: > Mike, > > Wouldn't number 10 be a massive amount of unnecessary work and replication? > I was under the impression that if you had replication going between the two > arrays and you suspended the replication, that you could bring up the > replication targets in a read/write mode on the new servers. If you had to > back out, after shutting the new servers down, you could "unsuspend" the > replication and data that had changed on the source volumes would be > replicated to the targets, and data on the targets that had changed would > also have the source data pushed to overlay the changed targets. Is this not > how replication works? > > Rex > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf > Of Mike Schwab > Sent: Tuesday, February 14, 2012 2:59 PM > To: [email protected] > Subject: Re: Changing sysplex hardware > > Since you are moving the entire datacenter and all dasd is already > replicated, then. > Old location: > 1. Shut down your existing systems. > Old location prefered. > 2. Break dasd replications. > New location. > 3. IPL one system. > 4. Start Sysplex using your new datasets. > 5. IPL the other systems. > > Backout: > New location > 6. Shut down your systems at new locations. > Old Location. > 7. IPL one system. > 8. Start Sysplex using your old datasets. > 9 IPL the other systems > When up: > 10. Restart replication from scratch for next try. The secondaries > will have been updated (access date at a minimum), so restarting a > suspended replication would result in bad volumes. -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN The information contained in this e-mail may contain confidential and/or privileged information and is intended for the sole use of the intended recipient. If you are not the intended recipient, you are hereby notified that any unauthorized use, disclosure, distribution or copying of this communication is strictly prohibited and that you will be held responsible for any such unauthorized activity, including liability for any resulting damages. As appropriate, such incident(s) may also be reported to law enforcement. If you received this e-mail in error, please reply to sender and destroy or delete the message and any attachments. Thank you. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
