Bacula-users

Re: [Bacula-users] file set changes with accurate mode enabled

2015-05-19 04:20:36
Subject: Re: [Bacula-users] file set changes with accurate mode enabled
From: Pavel Bychikhin <pbychikhin AT yahoo DOT com>
To: Radosław Korzeniewski <radoslaw AT korzeniewski DOT net>
Date: Tue, 19 May 2015 11:14:45 +0300
Radosław,
According to your explanations, I've understood that using dynamic filesets with "<" at the beginning with Accurate mode enabled is the same as using "Ignore FileSet Changes=yes" with Accurate mode enabled. Am I right?
Will you, in general, recommend using dynamic filesets with "<" at the beginning or it is better to avoid such setups? Are there any pitfalls I have to be aware about?
Thank you
Best regards,
Pavel

-------- Original Message --------
Subject: Re: [Bacula-users] file set changes with accurate mode enabled
From: Radosław Korzeniewski <radoslaw AT korzeniewski DOT net>
To: Pavel Bychikhin <pbychikhin AT yahoo DOT com>
Cc: bacula-users <bacula-users AT lists.sourceforge DOT net>
Date: 18.05.2015 19:55
Hello,

2015-05-13 9:35 GMT+02:00 Pavel Bychikhin <pbychikhin AT yahoo DOT com>:
Hi Radoslaw,
Thank you very much for your answer.
I have one more in this regard. Can you please clarify it for me as well.
One of my File definitions looks like:
    File = </usr/local/etc/bacula/some_file_name 
In this case if I add some new lines to that file, bacula will not force Full backup and will not backup that new files if accurate mode is disabled.
I feel myself a little bit confused since in this situation bacula doesn't follow its logic of file set tracking. Looks like it just ignores such filesets while doing incremental backup and relies on a file set definition which was stored at the time of last Full backup. And Accurate mode magically solves this issue.

First of all the Bacula (to be more specific Director) is checking a fileset changes by computing a md5 digest on the fileset Include/Exclude definition and stores it in the catalog. If computed digest is the same as a previous then Director decides that a fileset definition is not changed. So incremental backup is not changing its level. In your example the fileset is not changed but a File Daemon is responsible for listing files to backup. If you make this king of configuration you should know what you are doing.
 
best regards
--
Radosław Korzeniewski
radoslaw AT korzeniewski DOT net

------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
<Prev in Thread] Current Thread [Next in Thread>