On Mon, 6 May 2024, Kirby wrote: > BackupPC has been covering up my stupid mistakes since 2005. Fortunately, I > have never done the 'rm -r *' until last week. Good thing was that I was in my > home directory so the system itself was untouched and I caught myself before > too much could get deleted. > > 'Not a problem!' I thought. I will just restore from last night's backup and > be on my way. I selecting the missing files and directories, started the > restore, and went for a walk. When I got back things were in a sorry state. My > ~/Downloads directory was has filled up my drive included stuff that had been > deleted 5 years ago. > > Am I misunderstanding how fill works? I though it was filled from the last > backup going back to the last non-filled backup. Instead it looks like it is > pulling everything it has ever backed up. > > I am running BackupPC-4.4.0-1.el8.x86_64.
My guess is you were backing up using rsync, and using the default flags to rsync that backuppc specifies, which is to not supply --ignore-errors. Then you were backing up a filesystem that had IO errors (/home/$user/.cache/doc), so rsync was not sending the file deletions to backuppc, so backuppc was operating under the assumption that the files you had deleted in the meantime were all still there. Unfortunately, the only bug I know asking to include --ignore-errors by default, has been closed without that fix included: https://github.com/backuppc/backuppc/issues/87 Also unfortunately, this will affect all your previous backups, so there's no way of recovering what your filesystem actually looked like lastnight. -- Tim Connors _______________________________________________ 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/
