> ...I was hoping someone would have > experience with a high-speed backup product that would backup open > files for U2. Since our application has a module that uses > ASP.NET we really don't want to shut down the dbms for very long > (this is more important than backuping up open files and not having > a "pristine" backup).
It's pretty common to use an extra mirrored copy or a flash copy to provide backups of a quiescent database without suspending processing. It goes like this: 1) Pause updates with dbpause 2) Split off the copy, which will now be as of a point in time 3) Resume updates with dbresume 4) Back up from the quiescent, split copy, using the backup utility of your choice 5) Resync, snap back or do whatever is necessary to get the copy back up to date The duration of the pause will depend on many factors, but it's usually pretty quick - generally measured in seconds rather than minutes. And of course the exact commands to perform steps 2 and 5 will vary based on your operating system, disk storage facilities, high availability options, etc., etc. If your application uses transaction processing semantics, the transactions will be consistent within the backup, thanks to the dbpause. And you won't have to worry about files being backed up while groups are being updated, since they're not being accessed by the production users, who are happily going about their business, regardless of how long the actual backup takes. 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/
