On Wed, Aug 21, 2024 at 6:49 AM Ghislain Adnet <gad...@aqueos.com> wrote:
>
> anyway the issue is here to spot and correct problems. If there is a way, be
> it in the rsync options or backuppc system i would gladly hear it as perhaps
> i missed something somewhere :)
>
If your full backups will complete with the --ignore-times option
mentioned above (as v3 would have used), I'd just do that so you'll
get a check on every unchanged file at whatever interval you do full
runs. These will probably already be skewed to do different machines
on different nights and if they aren't you can force a run to tweak
the timing. However your real effort should be toward finding/fixing
the source of the corruption. It won't help much to make more copies
on a drive that is going to lose it anyway. I usually tried to use
software raid1 as the storage medium so you have several chances of
recovery from either a drive or controller issue. And if you have
multiple locations with good connectivity, run another backuppc
instance in a different location. The price is right for the software.
--
Les Mikesell
l...@gmail.com
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/
