Steve,
Correct! A Point in Time. However, it is only providing this facility because the IBM hardware cannot. If you are using HDS Shadowimage At-Time split then there is no need to disrupt your DB2 processing with Log Suspend/Resume. There seems to be an impression that DB2 Log Suspend/Resume magically does something magical with in-flight transactions. Remember the post from Phil Steele: "the only issue I see is that if you want a nice consistant database that is already complete just like it had been shut down in an orderly manner and didn't need any recovery at all, then a quiece before flash copy commencement would be needed." Unfortunately for Phil, DB2 Log Suspend/Resume does not do what he described. The only way to get that pristine environment is to shutdown DB2 in an orderly manner. Ron > 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
