Thank you for the clarification, Tim. Much appreciated. I am still not finding any real documentation details on UV's SUSPEND.FILES ON/OFF.
Does this indeed work in the same manner as DBPAUSE and DBRESUME, where a "sync" operation is performed to all memory resident files to ensure they write out contents to the disk files? One other clarification question on this while it's on the table. If a Customer, or a Customers application, is not using Transaction Logging they indeed run the risk of being transactionally in-consistent in either scenario - running [UD] DBPAUSE / DBRESUME or [UV] SUSPEND.FILES ON/OFF and/or stopping [UD] or [UV]. Agreed, I would suspect it is much better to be database consistent with the possibility of some "transactions in progress" be in-consistent, and "generally speaking" depending on the actual applications and their transactions - some applications may tend to lend themselves to be more severely afftected by transactional-integrity sensitive than others. (Of course - with the caveat of "your actual mileages may vary"). Regards, Scott Richardson * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * Prime Information / UniVerse / Unidata / Sequoia PICK / mvBase Pr1me Computer \ Encore Computer Corporation \ Sequoia Systems * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * Senior Systems Engineer / Consultant Product Support Engineer * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * ----- Original Message ----- From: "Timothy Snyder" <[EMAIL PROTECTED]> To: <u2-users@listserver.u2ug.org> Sent: Thursday, July 05, 2007 9:23 AM Subject: Re: [U2] UD Backups - DBPAUSE for UniVerse? > > For any Backup solution that uses the Microsoft VSS Snapshot > > functionality, or an "Advanced Open File Manager" option, would it be > > safe to say that for UD applications, they should issue the DBPAUSE > > command, "grab a snapshot", then DBRESUME - *for each Backup > > requested*, to ensure optimal consistency of the Backup's integrity? > > Since others have responded with the information about suspending updates > on UV, I'll focus on this question about using snapshots. The answer for > both UDT and UV is yes, for each backup requested you should suspend > updates, create the snapshot, resume updates, and then back up from the > snapshot. This gives you safe backups that are consistent as of a point > in time. Note, however, that if your application doesn't have transaction > processing semantics in place, the backup may be transactionally > inconsistent. In other words, if you don't tell the database where the > logical transactions begin and end, it's possible that only some files in > a transaction will have been committed as of the time of the backup. Of > course, you would have the same issue even if you logged off all users to > perform the backup, and the pause-snapshot-resume scenario is much more > appealing than doing that or (worst of all) backing up the database while > hot. > > Tim Snyder > Consulting I/T Specialist > U2 Lab Services > Information Management, IBM Software Group > ------- > u2-users mailing list > u2-users@listserver.u2ug.org > To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
