RE: [U2] UD Backups - DBPAUSE for UniVerse? [not-secure]
snip I am still not finding any real documentation details on UV's SUSPEND.FILES ON/OFF. /snip As an aside, I suspect you are suffering from the poor organization of the UniVerse documentation. I would expect something like this to be in a guide for administrators, yet SUSPEND.FILE is documented is the user reference. (It does get one sentence in the Administering UniVerse guide...)... Then there are items in the System Description that should be somewhere else. It's one thing to use the system description to talk about the existence of file triggers, but to use that as the place to document the whole functionality it counter intuitive. --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] UD Backups - DBPAUSE for UniVerse? [not-secure]
I thought DBPAUSE allowed running processes to finish but would hold new processes . That's not much of a pause when you think that a process could be running for hours before the system is truly paused. From the online help: 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. Ron Sharcott (3635) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hennessey, Mark F. Sent: Thursday, July 05, 2007 8:34 AM To: u2-users@listserver.u2ug.org Subject: RE: [U2] UD Backups - DBPAUSE for UniVerse? [not-secure] snip I am still not finding any real documentation details on UV's SUSPEND.FILES ON/OFF. /snip As an aside, I suspect you are suffering from the poor organization of the UniVerse documentation. I would expect something like this to be in a guide for administrators, yet SUSPEND.FILE is documented is the user reference. (It does get one sentence in the Administering UniVerse guide...)... Then there are items in the System Description that should be somewhere else. It's one thing to use the system description to talk about the existence of file triggers, but to use that as the place to document the whole functionality it counter intuitive. --- 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/
RE: [U2] UD Backups - DBPAUSE for UniVerse? [not-secure]
I thought DBPAUSE allowed running processes to finish but would hold new processes . That's not much of a pause when you think that a process could be running for hours before the system is truly paused. Fortunately, that's not true. Only pending writes are processed, not entire programs. Committed transactions are processed, uncommitted transactions are temporarily rolled back. Processes that attempt new updates after dbpause is issued will appear to be hung. As soon as dbresume is issued, they pick up at the update. Processes performing read operations continue along their merry way. As a rule, control returns from dbpause to its invoking process in a few seconds, although it could be a bit longer if there are many pending updates or if it takes a long time for the disk subsystem to catch up. 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/
