Well, after doing a stat on many, many files, it appears that Nautilus
or some other application (possibly updatedb) is modifying the
timestamps on every file on the system. There is no virus checker as
this is a Linux system.
Placing mtimeonly=yes in the Options seems to take care of the problem.
Well, after doing a stat on many, many files, it appears that Nautilus
or some other application (possibly updatedb) is modifying the
timestamps on every file on the system. There is no virus checker as
this is a Linux system.
Placing mtimeonly=yes in the Options seems to take care of the problem.
@lists.sourceforge.net
Subject: Re: [Bacula-users] Incremental is really a full on FC6
What you've said makes sense to me too, but when I check the logs, it
shows that the files that were saved were compressed. Here's the full
log for the incremental:
29-Mar 23:05 backup-dir: Start Back
* Ridley schrieb am 30.03.07 um 22:52 Uhr:
> What you've said makes sense to me too, but when I check the logs, it
> shows that the files that were saved were compressed. Here's the full
> log for the incremental:
[...]
> JobId: 4
> Job:gandalf.2007-03-29_
What you've said makes sense to me too, but when I check the logs, it
shows that the files that were saved were compressed. Here's the full
log for the incremental:
29-Mar 23:05 backup-dir: Start Backup JobId 4,
Job=gandalf.2007-03-29_23.05.00
29-Mar 23:05 backup-sd: Volume "Vol-0002" previously w
* Ridley schrieb am 30.03.07 um 13:31 Uhr:
> I have Bacula backing up only /home on a Linux workstation running FC6.
> This is the Fileset:
>
> FileSet {
> Name = "Home Set"
> Include {
> Options {
> signature = MD5
> compression = GZIP
> Exclude = yes
> WildFile =
I have Bacula backing up only /home on a Linux workstation running FC6.
This is the Fileset:
FileSet {
Name = "Home Set"
Include {
Options {
signature = MD5
compression = GZIP
Exclude = yes
WildFile = "/home/*/.mozilla/firefox/*/Cache/*"
WildFile = "/home/*/.m
