On Wednesday 2017-03-29 14:07:43 scar wrote:
> Josip Deanovic wrote on 03/28/2017 09:10 PM:
> > I believe that this could be a problem.
> > It could be that bacula saved files with ctime during the last full
> > backup and now sees all the files as changed even with the "mtimeonly"
> > set to "yes"
Josip Deanovic wrote on 03/28/2017 09:10 PM:
> I believe that this could be a problem.
> It could be that bacula saved files with ctime during the last full
> backup and now sees all the files as changed even with the "mtimeonly"
> set to "yes".
>
> If this is the case it would be a good idea to ch
On Tuesday 2017-03-28 19:44:17 scar wrote:
> I am using bacula 5.x and I recently replaced the hardware for a client
> (new machine). I used "rsync -a" to copy over the contents of one of
> the filesystems. Now bacula wants to back up everything again even
> though nothing is changed. The filesy
I am using bacula 5.x and I recently replaced the hardware for a client
(new machine). I used "rsync -a" to copy over the contents of one of
the filesystems. Now bacula wants to back up everything again even
though nothing is changed. The filesystem is the same and the path to
the files is t
