Hi, all. First of all, a little background...
I'm in the process of setting up a large new disk- and tape-based backup server using Bacula 1.36.3. We expect the server to handle the backups of between 20 and 30 other servers. Initial counts show that we'll be grabbing about 110GB (totalling just short of 10,000,000 files) for each full backup. We're using a 1.3TB SATA RAID disk array for the majority of the backups (monthly full, weekly diff, daily inc) and will also be doing a full backup to an AIT-3 tape drive on a schedule yet to be determined so we have something off-site as well. With 10,000,000 files right off the bat, I'm a bit concerned about catalog size. We've got about 100GB of space to work with for catalog storage, but I'm mostly concerned with the File table growing extremely large. By my calculations, a single full backup will add about 1.5GB to the File table's size. To combat this, I'm hoping to use several catalogs. What I wasn't able to figure out from the manual is whether or not I can keep all 20-30 servers backing up to one pool and still have them spread out over several catalog databases. Is this possible? If so, are there any drawbacks? If not, what's the best way to proceed? Thanks! -Brian -- I live in the United States of America, where we are gradually coming to understand that nothing we do is ever our fault, especially if it is really stupid. --Dave Barry, "The Tide is high and other household problems" ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
