This is what you said Pieter (NL)
>
> Did you look, with for example wx-console, if the files you didn't want to
> be
> backed up are indeed excluded to make sure if your fileset is or isn't the
> problem
>
> Pieter
>
>
> --
> View this message in context:
> http://www.nabble.com/Backups-too-big%2C-and-other-questions-t1502635.html#a4083663
> Sent from the Bacula - Users forum at Nabble.com.
Backing up the sparse file (1.2TB in size (64K actual size)), with the
spase otion enabled for the file, still takes about 2.5 hours to backup.
Does this sound correct?
That is an improvement on the 7 hours without sparse enabled, but I would
have guessed that backing up a sparse file whose actual file size is 64K
would only take a matter of seconds.
Here is the new FileSet with the sparse option enabled:
FileSet {
Name = "Firewall Full"
Include {
Options {
signature = MD5
sparse = yes
compression = GZIP
}
File = /var/log/lastlog
}
Include {
Options {
compression = GZIP
signature = MD5
wildfile = "/var/log/lastlog"
wildfile = "/.journal"
wildfile = "/.fsck"
wilddir = /proc
wilddir = /tmp
wilddir = /sys
wilddir = /dev
wilddir = /mnt
wilddir = /BACKUPS
wilddir = /var/spool/squid
Exclude = yes
}
File = /
File = /boot
File = /home
File = /var
}
}
I could probably remove /wildir = /BACKUPS as /BACKUPS is its own
filesystem, but I included it for readability.
If this is still not the correct way to handle the sparse file, please let
me know.
Thanks.
Scott
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
