After a failed incremental backup, my last *old* *good* backup was
renumbered.
Specifically before the failed backup:
484 incr yes 1 2021-01-12 01:00 3.5 0.9
482 incr no 1 2021-01-11 01:02 8.1 1.9
481 full yes 0 2021-01-10 01:00 33.8 2.9
After failed backup:
484 incr yes 1 2021-01-12 01:00 3.5 0.9
483 incr no 1 2021-01-11 01:02 8.1 1.9
481 full yes 0 2021-01-10 01:00 33.8 2.9
The log shows the following:
2021-01-12 01:03:32 incr backup 483 complete, 309199 files, 25749468485
bytes, 0 xferErrs (0 bad files, 0 bad shares, 0 other)
2021-01-12 01:03:32 Removing unfilled backup 466
2021-01-12 01:03:32 BackupPC_backupDelete: removing #466
2021-01-12 01:03:32 BackupPC_backupDelete: No prior backup for merge
2021-01-12 01:03:38 BackupPC_refCountUpdate: host consult got 0 errors
(took 5 secs)
2021-01-12 01:03:38 Finished BackupPC_backupDelete, status = 0 (running
time: 6 sec)
2021-01-12 20:42:40 incr backup started for directory root (client path
/mnt/btrfs-root/@_snapshot-backuppc-20210112-204239)
2021-01-12 20:42:41 Got fatal error during xfer (rsync error: error in
rsync protocol data stream (code 12) at io.c(226) [Receiver=3.1.2.2])
2021-01-12 20:42:46 Backup aborted (rsync error: error in rsync protocol
data stream (code 12) at io.c(226) [Receiver=3.1.2.2])
2021-01-12 20:42:46 Removing empty backup #483
2021-01-12 20:42:46 BackupPC_backupDelete: removing #483
2021-01-12 20:42:46 BackupPC_backupDelete: Merge into backup 482
2021-01-12 20:43:01 BackupPC_refCountUpdate: host consult got 0 errors
(took 15 secs)
2021-01-12 20:43:01 Finished BackupPC_backupDelete, status = 0 (running
time: 15 sec)
where #466 was an expiring (incremental) - note it was created ~2 weeks
earlier per the following log line:
2020-12-26 01:02:51 incr backup 466 complete, 309576 files, 25813786934
bytes, 0 xferErrs (0 bad files, 0 bad shares, 0 other)
So, why does an aborted backup cause the old (good) backup #483 to
jump to #484, leaving an empty backup in #483.
I assume this is due to how backups are merged forward -- but it would
be nice, if this were undone, when a backup is aborted -- if only to
keep the backup history tight and consistent. Indeed, this
renumbering, can make it hard to "track" backups as their numbers can
change.
_______________________________________________
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/
