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 [email protected] To <[email protected]> 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 [email protected] To unsubscribe please visit http://listserver.u2ug.org/
