In my previous life, long before the advent of mirroring, we decided on a 'system-managed backup/recovery' strategy. It was clear to us that we could not trust the applications folks to tell us the whole truth. They weren't malicious; they just didn't always know but would not admit even to themselves that they didn't know.
Ambrose Bierce in the Devil's Dictionary. Definition of 'positive'--adj. Mistaken at the top of one's voice. We took it upon ourselves to backup and restore everything on the floor. Decades later with ficon XRC, we do the same thing today. No qualms. . . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-302-7535 Office [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Scott Chapman Sent: Friday, May 20, 2016 5:58 AM To: [email protected] Subject: (External):Re: Mirror/back up your Development DASD In addition to the other reasons cited, one of my arguments was that I wasn't 100.00% sure that the app team hasn't squirreled something away in a non-production storage group that really was needed for either running or fixing or recovering production. And the chance for human error sneaking in when you're setting up the list of volumes to replicate likely increases if the rule is "replicate only some of the volumes" vs. "replicate all volumes". Scott ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
