Cedric Tefft a écrit :
>
> Run "stat" on one of those older files. Look at the ctime. Is it
> very recent -- perhaps a day or less? By default, bacula uses both
> the mtime and ctime of a file to determine if it has been changed. If
> EITHER one of those is newer than the last backup, bacula
Guillaume_h wrote:
> Kevin Keane a écrit :
>
>> Bacula uses the file date to determine which files have changed. So a
>> file with a future file date would be backed up by each incremental backup.
>>
>> Since you say that your file was NOT backed up on 9/15 and 9/16, my
>> guess is that some
Kevin Keane a écrit :
> Bacula uses the file date to determine which files have changed. So a
> file with a future file date would be backed up by each incremental backup.
>
> Since you say that your file was NOT backed up on 9/15 and 9/16, my
> guess is that some application may be opening the f
Bacula uses the file date to determine which files have changed. So a
file with a future file date would be backed up by each incremental backup.
Since you say that your file was NOT backed up on 9/15 and 9/16, my
guess is that some application may be opening the file for writing
without actual
le dahut a écrit :
The problem occurred after a while, here's an history that illustrates
what's happening :
09/14:
Backup Level: Full
FD Files Written: 6,489
on 09/15 and 09/16:
Backup Level: Incremental, since=2009-09-15 23:00:15
FD Files Written: 50
09/
The problem occurred after a while, here's an history that illustrates
what's happening :
09/14:
Backup Level: Full
FD Files Written: 6,489
on 09/15 and 09/16:
Backup Level: Incremental, since=2009-09-15 23:00:15
FD Files Written: 50
09/17:
Backup Level:
