We also have all EMC dasd. To guard against application faux pas that are not immediately discovered, we maintain 3 copies of TPF at 8 hour intervals (we can also bring home our offsite copies, which you need to be able do when a real disaster is over). For DR testing, we snap off point-in-time copies of TPF, z/OS, z/VM, and z/Linux (ECKD) dasd. We bring up TPF under our z/VM at the DR site so we can remap devices to correspond with the vendor provided hardware environment. It all works like a charm. Once the vendor moves our dasd over, we IPL z/VM, check the hardware environment, then un-NOLOG TPFPROD, and IPL it. Getting the network switched over takes more time than this, so we wind up waiting on them.
________________________________ From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Schuh, Richard Sent: Wednesday, November 10, 2010 7:51 PM To: IBMVM@LISTSERV.UARK.EDU Subject: BRP Finally, the powers that be are considering remote shadowing of DASD as the way to handle the BRP situation. The time we are allotted to recover the system has been reduced to a number that is impossible using tape backups. I would appreciate it if anyone who is already doing this would regale me of their experiences - what they are doing, what are the gotchas, how satisfied are they, etc. It undoubtedly is different depending on the dasd vendors so here is what we have: * EMC DASD - about half of our DASD. * HDS DASD - the other half. * Currently, there is no SCSI, it is all ECKD We currently have no IBM DASD; however, that does not mean that we will not have some in the future. Every couple of years, we go through a DASD refresh, at which time we may change vendors. I will gladly accept replies on or off list. TIA. Regards, Richard Schuh
