Hi, I realized that I have one host where I have a backup history going back only 47 days while on all other hosts I have roughly 2 years. I am using the following settings for all hosts:
FullPeriod=6.97 FillCycle=0 FullKeepCnt=[3, 0, 3, 0, 6] FullKeepCntMin=3 FullAgeMax=720 That should give me app. 3*1 weeks + 3*4 weeks + 6*16 weeks = 111 weeks (a bit over two years). On that host, the backup summary says: 37 incr filled level 1 age 0.4 36 incr no level 1 age 1.4 35 full filled level 0 age 2.7 33 incr no level 1 age 4.2 32 incr no level 1 age 5.4 31 incr no level 1 age 6.4 30 incr no level 1 age 7.4 29 incr no level 1 age 8.4 27 full yes level 0 age 10.7 21 full yes level 0 age 18.3 0 full yes level 0 age 39.7 On all other hosts the backup numbers (first column above) are in the hundreds. The host logs say the following: 2023-02-26 14:44:59 full backup started for directory / 2023-02-26 14:46:02 full backup started for directory /home 2023-02-26 16:34:32 full backup started for directory /usr/local 2023-02-26 16:34:37 full backup started for directory /var 2023-02-26 16:50:30 full backup started for directory /boot 2023-02-26 16:50:42 full backup started for directory /mnt/data 2023-02-26 17:26:37 Removing prior partial backup #591 2023-02-26 17:26:37 BackupPC_backupDelete: removing #591 2023-02-26 17:26:37 BackupPC_backupDelete: Merge into backup 590 2023-02-26 17:27:32 BackupPC_refCountUpdate: host serv got 0 errors (took 42 secs) 2023-02-26 17:27:32 Finished BackupPC_backupDelete, status = 0 (running time: 55 sec) 2023-02-26 17:27:33 full backup 592 complete, 552150 files, 324702757005 bytes, 3 xferErrs (0 bad files, 0 bad shares, 3 other) Then there are a couple of incremental backups and then this: 2023-03-05 20:21:53 full backup started for directory / 2023-03-05 20:22:25 full backup started for directory /home 2023-03-06 00:34:46 full backup started for directory /usr/local 2023-03-06 00:34:52 full backup started for directory /var 2023-03-06 00:48:25 full backup started for directory /boot 2023-03-06 00:48:34 full backup started for directory /mnt/data 2023-03-06 01:30:16 Aborting backup up after signal TERM 2023-03-06 17:00:00 Removing unfilled backup 590 2023-03-06 17:00:00 BackupPC_backupDelete: removing #590 2023-03-06 17:00:00 BackupPC_backupDelete: No prior backup for merge 2023-03-06 17:16:38 BackupPC_refCountUpdate: serv #599 inodeLast set to 2422703 (was 2422241) 2023-03-06 18:00:02 full backup started for directory / 2023-03-06 18:07:17 full backup started for directory /home 2023-03-07 08:30:01 Renaming /var/lib/backuppc/pc/serv/XferLOG.0.z -> /var/lib/backuppc/pc/serv/XferLOG.0.z.tmp 2023-03-07 08:30:04 full backup started for directory / 2023-03-07 08:35:37 full backup started for directory /home 2023-03-07 11:57:12 full backup started for directory /usr/local 2023-03-07 11:57:24 full backup started for directory /var 2023-03-07 12:13:53 full backup started for directory /boot 2023-03-07 12:14:08 full backup started for directory /mnt/data 2023-03-07 13:50:18 full backup 0 complete, 555670 files, 335367981491 bytes, 3 xferErrs (0 bad files, 0 bad shares, 3 other) So apparently BackupPC did not take the "Aborting backup up after signal TERM" very well. This host is the backup server, backing up itself. But I don't quite understand why it decided to throw away the entire backup history and start over from 0? And more importantly, is there something I could do to prevent this from happening again, other than avoiding shutdowns in the middle of a backup? Fabian _______________________________________________ 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/
