>>>>> On Mon, 21 Dec 2009 16:27:49 -0700, Robert LeBlanc said:
>
> So, I've run into an interesting problem with 3.x. We have our servers
> configured for separate root, home and log partitions usually using LVM.
> I've seen this in the past, but now I'm looking to find an answer. We are
> running 3.0.2 on Debian Squeeze, when we include the /var/log/ partition,
> either by using oneFS on or oneFS yes and specifying it, it explodes the
> size of the backup. For instance, here is the layout of the partitions for
> one machine:
> Filesystem Size Used Avail Use% Mounted on
> /dev/mapper/lsgw-root
> 2.3G 842M 1.3G 39% /
> tmpfs 502M 0 502M 0% /lib/init/rw
> udev 10M 176K 9.9M 2% /dev
> tmpfs 502M 0 502M 0% /dev/shm
> /dev/sda1 228M 25M 192M 12% /boot
> /dev/mapper/lsgw-home
> 938M 18M 920M 2% /home
> /dev/mapper/lsgw-logs
> 3.6G 77M 3.6G 3% /var/log
>
> If we exclude the /var/log/ partition, estimate give us:
> 2000 OK estimate files=40539 bytes=711,837,359
>
> When we include the /var/log/ partition using oneFS=no, estimate give us:
> 2000 OK estimate files=66741 bytes=233,544,784,662
>
> When we include the /var/log/ partition using oneFS=yes, estimate gives us:
> 2000 OK estimate files=40620 bytes=232,347,795,189
>
> df on the machine give us:
> du -sh /
> du: cannot access `/proc/4002/task/4002/fd/4': No such file or directory
> du: cannot access `/proc/4002/task/4002/fdinfo/4': No such file or directory
> du: cannot access `/proc/4002/fd/4': No such file or directory
> du: cannot access `/proc/4002/fdinfo/4': No such file or directory
> 800M /
>
> As you can see a far cry from 232 GB.
>
> I've tried accurate backups without any change and the estimate from
> experience is what is actually backed up so it's not just a bad figure in
> the estimate command.
>
> Here is my fileset def:
>
> FileSet {
> Name = "LinuxServer"
> Include {
> Options {
> signature = MD5
> onefs = yes
> exclude = yes
> wildfile = ".reiserfs*"
> wildfile = ".journal"
> wildfile = ".autofsck"
> wildfile = "*~"
> }
> File = "/"
> File = "/home"
> File = "/var/log"
> }
> }
>
> For some reason /home is not affected by this, only /var/log. What can I do
> to try to track down what is going on, for now, I'll have to exclude
> /var/log, but I'd like to get to the bottom of this.
Possibly you have sparse files in /var/log? Bacula can handle those better if
you use the sparse=yes option in the FileSet (see the doc for more).
__Martin
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
