Ghislain Adnet wrote at about 19:41:31 +0200 on Tuesday, August 20, 2024: > so what i get from this is that when there a corruption for a random reason > backuppc will see it but will not do anything to correct it or backup it > ever again even if it exist on the source client. > > This sound really bad to me beceause if this is true then we have no way of > recovering from this it seems. > > So we can all have thousands of files not backuped on our servers without > any way to correct this apart reinstalling a fresh backuppc system and pray > it does not do it again :(
First of all, the corruption seems almost definitely to be a disk issue and not a backuppc issue. You should be monitoring for disk corruption using various versions of RAID or advanced file systems independent of backuppc. Not sure why you would be blaming backuppc for that. Second, when files are missing from the pool, typically backuppc does warn in the logs. However, it doesn't necessarily make sense for backuppc to continuously check through an endless number of historical backups to see if there is corruption somewhere. Third, as others have pointed out you should regularly check yourself that your backups are intact. Such checks range from the simple like running Backuppc_fsck regularly or running file system integrity checks to the more comprehensive like writing your own routines to trawl through the pc and pool trees to look for errors (warning: they can take A LOT of time) or simulating a full to the metal restore. Finally, you should backup your backups. I run two independent versions of backuppc in my home situation with one running on a RPi4. _______________________________________________ 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/
