<quote who='Edward Brown' date='Thursday 14 August 2008'> > There's a dbpause / dbresume command on unidata that looks like it > would make backups safer.
If your system supports filesystem snapshots, a really effective means is to: 1) dbpause the database 2) take file system snapshot of database 3) dsresume the database 4) perform tape backup from snapshot 5) release the snapshot once backup completes This typically results in very little downtime (as long as it takes to pefrom a snapshot of the filesystem) often 5-10 seconds or less. Yes, you should wait a few seconds after dbpause to allow any pending writes to complete. > dbpause is a UniData system-level command that blocks most updates to > the database made in a UniData session. Any updates made from the > operating system level are not blocked. You can use this feature to > perform some tasks that normally require UniData to be stopped, such as > backing up your data. > When the dbpause command is issued, all current writes and transactions > complete before > UniData pauses. Updates are blocked until the system administrator > executes the dbresume command. > > Edward -- Jeff Butera, Ph.D. Administrative Systems Hampshire College [EMAIL PROTECTED] 413-559-5556 "Email gives the illusion of progress even when nothing is happening." unknown ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
