> 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/
