RE: [U2] UD Backups - DBPAUSE for UniVerse?
This is one of many reasons to do all reading and writing to the database by using subroutines built on the database. -Original Message- From: Hona, David S [mailto:[EMAIL PROTECTED] Sent: Thursday, July 05, 2007 8:49 PM To: u2-users@listserver.u2ug.org Subject: RE: [U2] UD Backups - DBPAUSE for UniVerse? If you want incomplete updates in your database backup, then continue without pausing your database updates... :) Since BASIC applications don't timeout in database read/write operations, it's not really an issue. As for being a 'feature' it is sort of like the scenairo you get with a record update lock contention issue, except with no clause to handle the 'pause'.. Therefore you application would just wait until it's update is serviced...external applications using APIs are a different kettle of fish. So the 'feature' bit being it's transparent to your application. It is what you want with legacy applications of all sorts of vintage. Regards David -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Haskett Sent: Friday, July 06, 2007 10:41 AM To: u2-users@listserver.u2ug.org Subject: RE: [U2] UD Backups - DBPAUSE for UniVerse? Stephen: Is this kind of bogus or kind of a feature. Considering all the different ways connections can be made to the dbms, all kinds of software would/could be failing if backups are done during a "dbpause" timeframe. :-( So it really does mean backups have to be very complex with RAID configurations and implementations. Bill --- 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? {Unclassified}
Better still...
The U2UG are launching a Wiki "Real Soon Now" (we've already got it on the
site, we're getting user feedback on the one we've chosen). There are a couple
of annoyances though, so we're not done with the final decision.
However
An article on different ways of doing backups would make an ideal collaborative
posting...
Regards
Brian
Unfortunately, that's one of many omissions of the manuals and online
help...I wonder if they have a dedicated resource for this task of
keeping the manuals up-to-date and useful.
Perhaps someone would like to volunteer to document and then submit a
list of 'known errors and omissions' for the UniVerse documentation set?
Then it can be submitted to IBM?
Regards
David
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of HENDERSON MIKE,
MR
Sent: Friday, July 06, 2007 6:30 AM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] UD Backups - DBPAUSE for UniVerse? {Unclassified}
Ah, yes there it is in the User Reference, like you said Mark.
BUT, on 10.1 anyway,
* 'SUSPEND.FILES' is not in the Index of the User Reference, you
have to search the document to find it.
* When you do find it, it doesn't say whether the Dynamic / Type
30 file headers (or anything else) are flushed to disk when you
SUSPEND.FILES ON, and
* The documentation for uv -admin [options] lists the effects of
the options but not what the switch settings are that you would have to
use to invoke the options
All in all, not amongst IBM's best documentation efforts
Regards
Mike
---
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?
If you want incomplete updates in your database backup, then continue without pausing your database updates... :) Since BASIC applications don't timeout in database read/write operations, it's not really an issue. As for being a 'feature' it is sort of like the scenairo you get with a record update lock contention issue, except with no clause to handle the 'pause'.. Therefore you application would just wait until it's update is serviced...external applications using APIs are a different kettle of fish. So the 'feature' bit being it's transparent to your application. It is what you want with legacy applications of all sorts of vintage. Regards David -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Haskett Sent: Friday, July 06, 2007 10:41 AM To: u2-users@listserver.u2ug.org Subject: RE: [U2] UD Backups - DBPAUSE for UniVerse? Stephen: Is this kind of bogus or kind of a feature. Considering all the different ways connections can be made to the dbms, all kinds of software would/could be failing if backups are done during a "dbpause" timeframe. :-( So it really does mean backups have to be very complex with RAID configurations and implementations. Bill --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] UD Backups - DBPAUSE for UniVerse?
Stephen: Is this kind of bogus or kind of a feature. Considering all the different ways connections can be made to the dbms, all kinds of software would/could be failing if backups are done during a "dbpause" timeframe. :-( So it really does mean backups have to be very complex with RAID configurations and implementations. Bill >-Original Message- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] On Behalf Of Stephen O'Neal >Sent: Thursday, July 05, 2007 11:52 AM >To: u2-users@listserver.u2ug.org >Subject: RE: [U2] UD Backups - DBPAUSE for UniVerse? > >Slight correction > >For both UD DBPAUSE and UV SUSPEND.FILES ON, as soon as you >initiate the command, all WRITES to the DB will stop. > >So, that batch process will stop at the next WRITE, and not >continue until the process ends! > > Steve > > Stephen M. O'Neal > U2 Lab Services Sales Specialist > Information Management, IBM Software Group --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] UD Backups - DBPAUSE for UniVerse? {Unclassified}
Unfortunately, that's one of many omissions of the manuals and online
help...I wonder if they have a dedicated resource for this task of
keeping the manuals up-to-date and useful.
Perhaps someone would like to volunteer to document and then submit a
list of 'known errors and omissions' for the UniVerse documentation set?
Then it can be submitted to IBM?
Regards
David
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of HENDERSON MIKE,
MR
Sent: Friday, July 06, 2007 6:30 AM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] UD Backups - DBPAUSE for UniVerse? {Unclassified}
Ah, yes there it is in the User Reference, like you said Mark.
BUT, on 10.1 anyway,
* 'SUSPEND.FILES' is not in the Index of the User Reference, you
have to search the document to find it.
* When you do find it, it doesn't say whether the Dynamic / Type
30 file headers (or anything else) are flushed to disk when you
SUSPEND.FILES ON, and
* The documentation for uv -admin [options] lists the effects of
the options but not what the switch settings are that you would have to
use to invoke the options
All in all, not amongst IBM's best documentation efforts
Regards
Mike
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] UD Backups - DBPAUSE for UniVerse? {Unclassified}
Ah, yes there it is in the User Reference, like you said Mark. BUT, on 10.1 anyway, * 'SUSPEND.FILES' is not in the Index of the User Reference, you have to search the document to find it. * When you do find it, it doesn't say whether the Dynamic / Type 30 file headers (or anything else) are flushed to disk when you SUSPEND.FILES ON, and * The documentation for uv -admin [options] lists the effects of the options but not what the switch settings are that you would have to use to invoke the options All in all, not amongst IBM's best documentation efforts Regards Mike -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hennessey, Mark F. Sent: Friday, 6 July 2007 3:34 a.m. To: u2-users@listserver.u2ug.org Subject: RE: [U2] UD Backups - DBPAUSE for UniVerse? [not-secure] I am still not finding any real documentation details on UV's SUSPEND.FILES ON/OFF. 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/ The information contained in this Internet Email message is intended for the addressee only and may contain privileged information, but not necessarily the official views or opinions of the New Zealand Defence Force. If you are not the intended recipient you must not use, disclose, copy or distribute this message or the information in it. If you have received this message in error, please Email or telephone the sender immediately. --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] UD Backups - DBPAUSE for UniVerse?
Slight correction For both UD DBPAUSE and UV SUSPEND.FILES ON, as soon as you initiate the command, all WRITES to the DB will stop. So, that batch process will stop at the next WRITE, and not continue until the process ends! Steve Stephen M. O'Neal U2 Lab Services Sales Specialist Information Management, IBM Software Group "Ron Sharcott" <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 07/05/07 09:50 AM Please respond to u2-users@listserver.u2ug.org To cc Subject 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) --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] UD Backups - DBPAUSE for UniVerse?
Yes, UV initiates a "sync" at the time of the SUSPEND.FILES ON command is initiated. If there are enough disk drives under the system, it should only take between 15 and 45 seconds. After the "sync" completes. it will move to the next command. Yes, unless you add Transaction Semantics, (BEGIN TRANSACTION...WRITE...WRITE...END TRANSACTION...TRANSACTION COMMIT) you will have inconsistent data. Yes, I will write, and have others review, a brief paper on how to perform valid backups in UD/UV and stick it on the web. At your service, Steve Stephen M. O'Neal U2 Lab Services Sales Specialist Information Management, IBM Software Group "Scott Richardson" <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 07/05/07 07:58 AM Please respond to u2-users@listserver.u2ug.org To cc Subject Re: [U2] UD Backups - DBPAUSE for UniVerse? ... 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 --- 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/
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] I am still not finding any real documentation details on UV's SUSPEND.FILES ON/OFF. 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 am still not finding any real documentation details on UV's SUSPEND.FILES ON/OFF. 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?
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: 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/
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/
RE: [U2] UD Backups - DBPAUSE for UniVerse?
>From the OS shell, uv -admin -L/R/U are synonyms to the SUSPEND.FILES TCL >command. The Users Reference guide documents both of these methods. Regards, LeRoy -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Manu Fernandes Sent: Thursday, July 05, 2007 4:16 AM To: u2-users@listserver.u2ug.org Subject: Re: [U2] UD Backups - DBPAUSE for UniVerse? SUSPEND.FILES ON/OFF Manu - Original Message - From: "Scott Richardson" <[EMAIL PROTECTED]> To: Sent: Wednesday, July 04, 2007 6:54 PM Subject: Re: [U2] UD Backups - DBPAUSE for UniVerse? >I have followed this thread with much interest. > > I have scoured the U2 / UniVerse documentation, but I see no > DBPAUSE command or equivilent for UniVerse. Are there any > commands with similar functionaility for UV, or does IBM have any > plans to introduce such command equilivents in UV as currently exist > in UD? > > 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? > > Would it also be safe to say that for UV Applications, the only sure > way to grab a consistent Backup of the UV environment would be > when the UV Database is shutdown, or in a state where there are no > users logged on and No PHANTOMs running? > > It would be nice if UV had the same operational level commands > that UD has in this area. > > I would appreciate any insight on this. > > Happy Indepedence Day / "Fourth of July" to all. > > Thank you. > 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: "Stephen O'Neal" <[EMAIL PROTECTED]> > Sent: Wednesday, June 27, 2007 8:16 PM > Subject: RE: [U2] UD Backups > > >> Colin Alfke asked: >> "Along that line - would there be anything else that may be holding up >> DBPAUSE?" >> >> A cause of a slow response back from DBPAUSE is not enough disk drives >> under a system. When DBPAUSE is initiated, it flushes all of the UDT >> disk >> buffers to disk. If there is a lot of data waiting to be written, it can >> take a while. >> >> Another cause, is when a single disk drive is hot. Example: if a file, >> that has a lot of updates, is on a single disk drive. Optimally, files >> with a lot of updates should be striped across multiple disk drives. >>Steve >> >>Stephen M. O'Neal >>U2 Lab Services Sales Specialist >>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/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] UD Backups - DBPAUSE for UniVerse?
SUSPEND.FILES ON/OFF Manu - Original Message - From: "Scott Richardson" <[EMAIL PROTECTED]> To: Sent: Wednesday, July 04, 2007 6:54 PM Subject: Re: [U2] UD Backups - DBPAUSE for UniVerse? I have followed this thread with much interest. I have scoured the U2 / UniVerse documentation, but I see no DBPAUSE command or equivilent for UniVerse. Are there any commands with similar functionaility for UV, or does IBM have any plans to introduce such command equilivents in UV as currently exist in UD? 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? Would it also be safe to say that for UV Applications, the only sure way to grab a consistent Backup of the UV environment would be when the UV Database is shutdown, or in a state where there are no users logged on and No PHANTOMs running? It would be nice if UV had the same operational level commands that UD has in this area. I would appreciate any insight on this. Happy Indepedence Day / "Fourth of July" to all. Thank you. 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: "Stephen O'Neal" <[EMAIL PROTECTED]> Sent: Wednesday, June 27, 2007 8:16 PM Subject: RE: [U2] UD Backups Colin Alfke asked: "Along that line - would there be anything else that may be holding up DBPAUSE?" A cause of a slow response back from DBPAUSE is not enough disk drives under a system. When DBPAUSE is initiated, it flushes all of the UDT disk buffers to disk. If there is a lot of data waiting to be written, it can take a while. Another cause, is when a single disk drive is hot. Example: if a file, that has a lot of updates, is on a single disk drive. Optimally, files with a lot of updates should be striped across multiple disk drives. Steve Stephen M. O'Neal U2 Lab Services Sales Specialist 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/
Re: [U2] UD Backups - DBPAUSE for UniVerse?
I have followed this thread with much interest. I have scoured the U2 / UniVerse documentation, but I see no DBPAUSE command or equivilent for UniVerse. Are there any commands with similar functionaility for UV, or does IBM have any plans to introduce such command equilivents in UV as currently exist in UD? 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? Would it also be safe to say that for UV Applications, the only sure way to grab a consistent Backup of the UV environment would be when the UV Database is shutdown, or in a state where there are no users logged on and No PHANTOMs running? It would be nice if UV had the same operational level commands that UD has in this area. I would appreciate any insight on this. Happy Indepedence Day / "Fourth of July" to all. Thank you. 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: "Stephen O'Neal" <[EMAIL PROTECTED]> Sent: Wednesday, June 27, 2007 8:16 PM Subject: RE: [U2] UD Backups > Colin Alfke asked: > "Along that line - would there be anything else that may be holding up > DBPAUSE?" > > A cause of a slow response back from DBPAUSE is not enough disk drives > under a system. When DBPAUSE is initiated, it flushes all of the UDT disk > buffers to disk. If there is a lot of data waiting to be written, it can > take a while. > > Another cause, is when a single disk drive is hot. Example: if a file, > that has a lot of updates, is on a single disk drive. Optimally, files > with a lot of updates should be striped across multiple disk drives. >Steve > >Stephen M. O'Neal >U2 Lab Services Sales Specialist >Information Management, IBM Software Group > --- --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
