Richard, How true. I thought this was part of the thinking behind "before" and "after" batch back-ups, providing a checkpoint where an application could be restored prior to some application related error or corruption.
There are a few sites that use in-system copy products (Shadowimage, FlashCopy, Timefinder, etc) to capture several Point-in-Time copies at regular intervals throughout the day to minimize the time required to restore and roll forward from this sort of error. From what I perceive of this problem, this sort of backup process may not have been compromised, and could have been used to restore the data to a recovery point in minutes, not days. There's a reason the storage vendor's are selling low performance, High Capacity SATA drives - this could be one of them :-) Ron > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of > Richard L Peurifoy > > Yes, but with mirroring it is already to late when the change occurs. > With a backup you have a chance to restore the bad data if you catch it > in time. We do backups every night, and keep them for at least a month. > The applications folks do their own backups as well, and may keep them > longer. > > It is certainly possible to not realize the problem until the backup > is no longer available, but at least you have a chance. > > -- > Richard > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
