On 13.02.2006, at 13:52, Dan Langille wrote:
On 13 Feb 2006 at 13:10, Sebastian Stark wrote:
On 13.02.2006, at 12:24, Sebastian Stark wrote:
On 13.02.2006, at 11:56, Michel Meyers wrote:
Sebastian Stark wrote:
After upgrading from 1.36.2 to 1.38.3 everything worked perfect
but one
job refuses to backup anything. An upgrade to 1.38.5 did not fix
this.
The FileSet definition did not change and there are definitely
files
that need to be backed up (new files, changed files..).
[...]
FileSet {
Name = "clusterhome set"
Include {
Options {
signature = MD5
exclude = yes
Not sure whether its related but this one is intriguing me. Why do
you
have exclude = yes there?
This is a remainder from early stages. But this fileset used to
work with 1.36 for months now. Do you think this could be a problem?
Seems like removing "exclude = yes" solves the problem. At least
estimate is not returning immediately. Thanks for pointing that out.
Obviously there have been changes to 1.38 that somehow changed the
way bacula interprets this (admittedly ambiguous) fileset.
I was going to suggest reading the release notes for possible changes
to FileSet directives.
I read the ReleaseNotes and found nothing regarding this, but in the
ChangeLog I found this innocent looking comment:
Changes to 1.37.7:
[...]
- Remove old style Include/Excludes.
[...]
I'll read a diff of the code before the next upgrade! :)
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
