Perhaps yours does the fsck too, but just very quickly so it may not be noticeable. Try running a backup manually, either full/incremental then watch the "Status" page. During the fsck, the "Host Summary" page will say "Backup in progress" whilst the "Status" page shows the actual task being performed, i.e. backing up, fsck, delete, etc. It would be best to try this on a host that has lots of files (1 million files+) and when you have more than 5 backups.
Regards,
Jimmy
I'm not certain, but I don't think my centos based v4 system is doing this. Do the fsck show in the log?
I will investigate when I get back to my computer.
It seems that BackupPC v4 runs fsck each time it does a backup, both incr or full. After an actual backup, it would run fsck on all the backups that it has for the host.
For example, host "pc1" has backup #1, #2, #3, #4, #5, #6, #7, and the new backup created #8. After BackupPC created backup #8, it would run fsck on #1, then on to #2, #3, #4, #5, #6, #7, #8 before it goes to "idle".
And when it runs again the next time to create backup #9, it would then run fsck all over again for all the backups (#1 - #9).
This makes each backup run for every host to take a very long time to finish and sometimes it takes longer than 24 hours to complete the whole fsck cycle against all the backups.
As a result, the backup lags behind and instead of a daily backup, I get backups that have gaps, be it a 1 day gap or 2+ day gap.
This is an issue for computers with a large number of files + a big total size of data.
Is this a normal behaviour? Is there something that can be done to improve this situation so that I have no gaps in my backups?