That's all fine and true. But Ghislain is touching a very valid point here.
He actually *did* test (or looked at BackupPC's fsck performing a partial
test), found out that there is some issue, and now wants to take steps to
resolve it.
If I understand correctly, the situation here is:
1) Backups have been executed in the past and been working fine.
2) Some corruption on the server happened; e.g., one or several pool files
experienced bit rot.
3) BackupPC_fsck detects the issue and reports a file as broken.
4) ... but there is no means for BackupPC itself to *react* on the issue; it
simply warns, but there is no recovery.
yes thanks this exactly this. As stated in the Subject of the thread.
I can have issue but then i need to be able to
- spot them
- correct them
in a programatic way (humans are unreliable).
Also
Backuppc_fsck
takes more than 24h on the backuppc server so cannot be used "regulary" without
preventing backuppc normal operations.
For PoolNightlyDigestCheckPercent
did it correct the issue of just put it in the logs ?
It seems it just do 1/ but not 2/ ;p
@Guillermo Rozas <guille2...@gmail.com> => thanks i think i will look at your
tool :)
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 :)
--
cordialement,
Ghislain ADNET.
AQUEOS.
_______________________________________________
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/
