Robert Porter wrote on 03/08/2004 12:35:29 PM: > What effect would this be to the users? Also I don't see a SUSPEND. > FILES in the online HELP, or the Administering guide. There is a > SUSPEND.RECOVERY command though. > > So if we were to implement this, would it be like this? > > 1) SUSPEND.FILES > 2) Snapshot the filesystem (then would I have a filesystem snapshot > with no pending UV writes?) > 3) (command to un-SUSPEND.FILES) > 4) Run the backup > 5) Undo the snapshot > > Any potential "gotchas" with doing this?
For the duration of the suspension, processes attempting to perform database writes will appear to hang until the suspension is removed. If you follow the procedures you've outlined, this will last for the duration of the snapshot - fairly minimal on most systems. The result will be, as you suspect, a quiescent copy of the database, with no worries about catching groups in mid-update. SUSPEND.FILES is documented in the UniVerse User Reference manual (and briefly in the admin manual). The commands are SUSPEND.FILES ON and SUSPEND.FILES OFF. If you're doing it from the O/S level, you may want to use the uv -admin -L option, which performs the same thing as SUSPEND.FILES ON. uv -admin -U will turn it off. This is a fairly common practice. I'm not aware of any gotchas. Tim Snyder IBM Data Management Solutions Consulting I/T Specialist , U2 Professional Services [EMAIL PROTECTED] -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
