Revisiting this old reported bug. Sometimes when a backup fails, the backup number of the *last* successful backup increases sequentially each time the backup fails.
For example, in a backup of Google Drive (mounted locally on my Linux system), I originally had: Backup# Type Filled Level StartDate 1096 incr no 1 2023-02-23 14:00 1095 incr no 1 2023-02-22 14:00 1094 incr no 1 2023-02-21 14:00 ... Then after about several days of failed backups, I had: 1159 incr no 1 2023-02-23 14:00 1095 incr no 1 2023-02-22 14:00 1094 incr no 1 2023-02-21 14:00 ... So that the old backup #1096 became #1159 -- even though no new backup was recorded. The failures happened because the fuser mount for google drive was failing. It seems like what happened is something like: 1. Last good (incremental backup) = N 2. Start active backup as N+1 -- so that backup N now becomes N+1 (so that when N+1 is completed, then N is re-created as a reverse delta relative to N_1 3. Backup N+1 fails (early?), so undoing #2, somehow leaves the old incremental relabeled as N+1 This cycle gets repeated for as many times as the backup fails leading to the last backup number being sequentially increased that many times. Note this doesn't happen with all failed backups (which is why presumably it has been hard to track down). But it seemed to happen in this case when the backup failed early due to the drive returning a mount error. Craig: Any ideas here? _______________________________________________ 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/
