* 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_23.05.00
> Backup Level: Incremental, since=2007-03-29 14:05:18
> Client: "gandalf" 2.0.3 (06Mar07)
> i686-redhat-linux-gnu,redhat,(Zod)
> FileSet: "Home Set" 2007-03-29 11:54:17
> Pool: "Default" (From Job resource)
> Storage: "File" (From Job resource)
> Scheduled time: 29-Mar-2007 23:05:00
> Start time: 29-Mar-2007 23:05:03
> End time: 30-Mar-2007 00:14:40
> Elapsed time: 1 hour 9 mins 37 secs
> Priority: 10
> FD Files Written: 38,621
> SD Files Written: 38,621
> FD Bytes Written: 31,923,730,782 (31.92 GB)
> SD Bytes Written: 31,930,104,420 (31.93 GB)
> Rate: 7642.7 KB/s
> Software Compression: 7.8 %
> VSS: no
> Encryption: no
> Volume name(s): Vol-0002|Vol-0003|Vol-0004
> Volume Session Id: 4
> Volume Session Time: 1175188894
> Last Volume Bytes: 1,040,824,645 (1.040 GB)
> Non-fatal FD errors: 0
> SD Errors: 0
> FD termination status: OK
> SD termination status: OK
> Termination: Backup OK
Indeed.
As it should be (or is?) possible to apply things like
compression only to files selected by a "wild = " or regx= option this is
a bit strange.
Kern can you clarify this? Are the following FileSets not correct?
Maybe this is only possible by creating more Include{} resources.
I dont know... maybe like this:
# 1. compress only *.txt and *.TXT files:
FileSet {
Name = OnlyCompressTxtFiles
Include {
Options {
compression = yes
regex = "^.*\.(txt|TXT)$"
}
File = /home
}
}
# 2. compress all but gzip'ed files
FileSet {
Name = CompressAllButGzipFiles
Include {
Options {
compression = no
regex = "^.*\.(gz|tgz)$"
}
Options {
compression = yes
}
File = /home
}
}
>
> 30-Mar 00:14 backup-dir: Begin pruning Jobs.
> 30-Mar 00:14 backup-dir: No Jobs found to prune.
> 30-Mar 00:14 backup-dir: Begin pruning Files.
> 30-Mar 00:14 backup-dir: No Files found to prune.
> 30-Mar 00:14 backup-dir: End auto prune.
>
> But the real problem is why the system is requiring a full backup even
> though it says it's an incremental. As far as I can tell, every single
> file was backed up on the incremental which tells me that something in
> FC6 is modifying something that Bacula looks at. I should note that when
> I was setting the configuration files up, I simply backed up /etc and
> the full and incremental backups worked as expected.
Bacula makes a full backup after you modified a FileSet, may this be
the cause?
Or may it be that all your files have a modification time in the future?
>
> In this situation, I manually ran the job after modifying the bacula-dir
> file to make sure it would work. I then let the system do an automatic
> backup last night and was suprized that over 30GB of data were backed
> up. I'm gonna run out of disk space in a hurry at this rate :-)
Yes..... have a deeper look at the files. And use
"estimate job=<jobname> level=Incremental listing"
in bconsole to test what would be done.
-Marc
--
begin LOVE-LETTER-FOR-YOU.txt.vbs
I am a signature virus. Distribute me until the bitter
end
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
