gregrwm wrote at about 19:24:17 -0500 on Monday, June 13, 2022: > i hadn't prepared my config quite as i'd intended, and expected a rather > long wait, so i interrupted BackupPC_dump. > on the next invocation i got: > 2022-06-12 21:35:02 Serious error: last backup > /var/lib/backuppc/pc/avocado/32 directory doesn't exist!!! Need to remove > back to last filled backup > 2022-06-12 21:35:02 Deleting backup 14 > 2022-06-12 21:35:08 Deleting backup 15 > 2022-06-12 21:35:14 Deleting backup 16 > 2022-06-12 21:35:20 Deleting backup 17 > 2022-06-12 21:35:27 Deleting backup 18 > 2022-06-12 21:35:34 Deleting backup 19 > 2022-06-12 21:35:41 Deleting backup 22 > 2022-06-12 21:35:47 Deleting backup 30 > 2022-06-12 21:36:00 Deleting backup 32 > > wow. not too robust! doesn't that seem like an inordinate consequence? >
I have encountered the same problem a couple of times in the past when I have interrupted backups. It seems that what happens is that somehow the reference backup gets corrupted, necessitating the erasure of all dependent non-filled backups. A similar, potentially related problem that I have run into is that when backups fail (independent of cancellations), the backup number gets incremented even though no new backup is recorded. I have reported both problems to Craig but have not been able to replicate it so no fix has been found. If you can reliably replicate the problem, then that should help nail down the problem, allowing for a fix. _______________________________________________ BackupPC-users mailing list [email protected] List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: https://github.com/backuppc/backuppc/wiki Project: https://backuppc.github.io/backuppc/
