> "The backup that is made between the SET LOG SUSPEND and the > SET LOG RESUME window might contain uncommitted data. If you > must restore the entire DB2 subsystem to the time when the > log was suspended, restore the entire database and logs from > the backup, and then restart DB2 to recover the entire DB2 > subsystem to a consistent state. For details, see DB2 Administration." > > > > Seems to me that Log Suspend just flushes the buffers, takes > a system checkpoint, and then stops your application from > writing anything until you do a resume. Rollback of in-flight > transactions is still going to take place. It is a nifty way > of getting a point in time across you DB2 Logs and tables > when the hardware can't do it. > > >From my reading that's what I understood DB2 to do when you issued a LOG SUSPEND in that it will provide a reliable and "firm" DB2 environment from which a point-time-copy can be made using any of the popular hardware vendor replication technologies that are out there.
Stephen Mednick Computer Supervisory Services Sydney, Australia ---------------------------------------------------------------------- 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
