What about the work in progress in DB2 buffers that is not yet committed (flushed) to DASD? The I/O might be consistent, but how would the data?
I would follow the suggestions in the DB2 doc rather than the hardware. Also, there is ample discussion in many recovery Redbooks that discuss the 'Point of Consistency' concepts and issues. Only the Lone Ranger has Silver Bullets. My US$0.02 -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Yi Ming Sent: Tuesday, July 12, 2005 5:31 AM To: [email protected] Subject: Re: DB2 and flashcopy2 Yup by quisce I mean DB2 "SET LOG SUSPEND" command to temporary suspend insert/update/delete activities. Looks like with Flashcopy v2 Freeze FlashCopy Consistency Group option, this is no longer necessary, the end results is still the same. Since DB2 won't be able to do any insert/update/delete activities as ESS will hold off I/O activity to a volume for a time period by putting the source volume in extended long busy state to obtain a consistent point-in-time copy of the related volume. But this makes for simpler PIT back operational procedures when backing up DB2. Regards, Yi Ming ---------------------------------------------------------------------- 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
