I believe this is documented in the Redbook as a PIT strategy using PTAM. PIT = point in time. PTAM = Pickup Truck Access Method. (It really says that!).
Missing from your strategy is POC = Point of Consistency. That is, your PIT backups need to be taken at a POC where all related files (be they system catalogs or DB2 tables) are logically consistent. Once that PIT backup is taken, you shouldn't use that application/resource any further until the whole process is complete. Just one example: you should not create any tapes once the RMM database is backed up. If you do, then those tapes would have to be managed as 'third party' or some such. But don't despair! Testing is the *only* way to shake these snakes out of the grass. HTH and good luck. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Longnecker, Dennis Sent: Tuesday, April 04, 2006 10:22 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Disaster Recovery, order of things Any thoughts on the best way to handle the backup of the various catalogs and RMM files for disaster recovery purposes? Thanks, Dennis Longnecker ---------------------------------------------------------------------- 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
