Alan Brown wrote:
On Wed, 24 May 2006, D Canfield wrote:

I'm just curious how other users are backing up maildirs using bacula. We're using cyrus as our mail server, so we've got about 162GB of data stored in 4.4 million files, or an average of 37K per message. Most other products I've tried (both commercial and open source) have not been too happy with this arrangement and end up requiring vast amounts of disk space and overhead to index this kind of mail spool.

I have similar numbers of similar sized files backed up as part of astronomical data.

Backing up is easy. Restoratation takes a while because of index generation, but the actual restore process is quick.

Does anyone know if bacula is any better with this? If not, I'm thinking my best resort would be to have each user's mail spool gzipped before backing it up

That wouldn't help much.
I think what Ryan is worried about is that Bacula's catalog DB's size is going to grow very big because of all the small files for which information has to be stored in it, day after day. (Incremental backup would help a little bit here already)

Is it possible to mount a zip file in loopback? Like one can do with an .iso file? Instead of an encrypted file system, does a compressed file system exist? Then he could simply rsync the folders with this file system mounted in loopback, unmount it and backup the files that sat underneath it. It might make sense to do that user per user to make the restore operation a little bit more practical.

Just brain storming...

Cheers,

Jo


-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to