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? Thanks, Robert >>> [EMAIL PROTECTED] 03/08/04 10:34AM >>> Robert Porter wrote on 03/08/2004 10:59:43 AM: > Since we're talking about a journalled filesystem, when the snapshot > completes the filesystem is in a consistent state. That's not to say > that UV couldn't be caching something itself that's not on disk. If you use SUSPEND.FILES or uv -admin -L before creating your quiescent copy, you can ensure that there's nothing "in motion" at the UniVerse level. 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 -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
