On Thu, 8 May 2008 09:59:37 -0500, Darth Keller <[EMAIL PROTECTED]> wrote:
>Hi Eric - > >Our SOP is that we mirror everything locally for DR. Once a day, we break >the link and back all the offline volumes up to tape. > >Doing every volume just makes the restore process at DR much simpler - >once the restore process is done, we ipl - no additonal steps like page >packs to set up, spool volumes to initialize, whatever. We're backing up >over 4,000 addresses - a lot of which are mod-27's. So even if we had 100 >page packs (mod-3's), it's not a real significant portion of the backup or >restore and isn't seen to be a big enough impact to change the procedure. > > >If the performance hit is small, there's no justification to changing the >process. But if it's significant... > One word: Bandwidth. The "one time" copy we do with SRDF makes sending all that useless data across the network unnecessary. We also don't mirror spool for all but a couple of very small environments (one sysplex has about 70 3390-3 volumes we don't mirror). We accept that anything in the spool at the time of a disaster is lost. This wouldn't be much as we have output control software. If network bandwidth wasn't a consideration, we would mirror everything as it does make the process simpler. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
