> This is equivalent to what we're doing now, but we're sort of one step up > in the hierarchy - backing up one tablespace at a time. > > You don't say whether you mean to back up each table to tape as it's > produced, or back them all up at the end when they've all been copied. > > Either way, there's problems.
I'll chime in with another potential solution: volume snapshots. In my day job, not using Bacula, we back up multi-terabyte Oracle databases every day. The database is in backup mode for only a few minutes per day. Granted, the length of time is probably more due to the EMC BCV cloning process, but the entire database is consistent, and whole backups are possible. If you're hosting your databases on a hardware SAN, this might be another option. Jeff Kalchik ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
