Hello, On 12.09.2005 21:43, Brian Keifer wrote:
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.
That should work.
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.
Good plan.
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.
Did you consider that the catalog only stores an entry for each unique filename? In other words, when you backup multiple servers running the same OS and some identical applications many of the file names will occur more than once, but only be stored once.
Your best bet to find a definitive answer is to try it, I guess... I, for example, save only a few machines here, but many of the file names on the windows machines aren't unique, and the same is true for the linux servers. And, for example, cyrus mail spool contains lots and lots of identical filenames in the mail folders.
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?
I don't know if it's possible, but I know that I'm not inclined to use multiple catalogs. One major drawback is that in the console you have to switch to the catalog valid for each client before you can do most useful tasks, and you can't get an overall view of your catalog data.
In fact, I assume that - implicitly - a pool always refers to a unique catalog.
Arno
Thanks! -Brian
-- IT-Service Lehmann [EMAIL PROTECTED] Arno Lehmann http://www.its-lehmann.de ------------------------------------------------------- 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