Sebastian Haas wrote:
>>>As the jobs started I've noticed the following message from the director:
>>>29-Sep 00:52 fileserver01-fd: DIR and FD clocks differ by -730 seconds,
>>>FD automatically adjusting.
>>>
>>>The director started the job at 1:05am while the FD's clock was 00:52.
>>>But I would assume that this is not a problem.
>>
>>
>>These two items are related. You have a clock drift problem on your
>>network. You might want to consider establishing a timeserver and
>>syncing all your internal machines to it, even if you don't actually
>>sync your timeserver to an external authoritative timeserver.
>
> Okay, fixed!
>
> Let us assume the problem is fixed due to the synchronized clocks, will
> an incremental backup (tonight) save files that it saved last night if
> they changed or will it not?
If they changed again today, they should be saved again; otherwise, not.
However, I don't expect this to fix your main problem; it will only fix
that "DIR and FD clocks differ" warning.
> What I try to say is, how bacula finds out which files needs to be
> backup incremental? On a per timestamp basis or on a content basis (e.g.
> MD5, SHA1, ...)?
The criterion used is creation/modification time. To checksum every
file on the machine simply to determine what to back up would take far
too long.
--
Phil Stracchino [EMAIL PROTECTED]
Renaissance Man, Unix generalist, Perl hacker
Mobile: 603-216-7037 Landline: 603-886-3518
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
