Backups - Is this a bug, and if so how do I report it?

Jeremy E

New Member
Jul 2, 2026
9
0
1
I have just noticed in the logs for my backups that the task is removing backups that I thought I was keeping... it appears as though it is treating the "Keep Hourly/Daily/Weekly/Monthly/Yearly" (under Retention) option the same as I would expect from "Keep Last". I'm sure it used to work as expected.

I see these - today (here) is the 22nd of November:

Code:
100: 2026-11-22 00:00:07 INFO: Starting Backup of VM 100 (lxc)
[truncated for brevity]
100: 2026-11-22 00:00:08 INFO: creating vzdump archive '/mnt/pve/WD5TB/dump/vzdump-lxc-100-2026_11_22-00_00_07.tar.zst'
[truncated for brevity]
100: 2026-11-22 00:01:01 INFO: prune older backups with retention: keep-weekly=1
100: 2026-11-22 00:01:01 INFO: removing backup 'WD5TB:backup/vzdump-lxc-100-2026_11_21-00_00_02.tar.zst'
100: 2026-11-22 00:01:01 INFO: pruned 1 backup(s) not covered by keep-retention policy

101: 2026-11-22 00:01:01 INFO: Starting Backup of VM 101 (lxc)
[truncated for brevity]
101: 2026-11-22 00:01:02 INFO: creating vzdump archive '/mnt/pve/WD5TB/dump/vzdump-lxc-101-2026_11_22-00_01_01.tar.zst'
[truncated for brevity]
101: 2026-11-22 00:02:18 INFO: prune older backups with retention: keep-weekly=1
101: 2026-11-22 00:02:18 INFO: removing backup 'WD5TB:backup/vzdump-lxc-101-2026_11_21-00_00_56.tar.zst'
101: 2026-11-22 00:02:18 INFO: pruned 1 backup(s) not covered by keep-retention policy

301: 2026-11-22 00:02:19 INFO: Starting Backup of VM 301 (lxc)
[truncated for brevity]
301: 2026-11-22 00:02:19 INFO: creating vzdump archive '/mnt/pve/WD5TB/dump/vzdump-lxc-301-2026_11_22-00_02_19.tar.zst'
[truncated for brevity]
301: 2026-11-22 00:03:45 INFO: prune older backups with retention: keep-weekly=1
301: 2026-11-22 00:03:45 INFO: removing backup 'WD5TB:backup/vzdump-lxc-301-2026_11_21-00_03_05.tar.zst'
301: 2026-11-22 00:03:45 INFO: pruned 1 backup(s) not covered by keep-retention policy

300: 2026-11-22 00:10:07 INFO: Starting Backup of VM 300 (lxc)
[truncated for brevity]
300: 2026-11-22 00:10:08 INFO: creating vzdump archive '/mnt/pve/WD5TB/dump/vzdump-lxc-300-2026_11_22-00_10_07.tar.zst'
[truncated for brevity]
300: 2026-11-22 01:05:18 INFO: prune older backups with retention: keep-monthly=1
300: 2026-11-22 01:05:18 INFO: removing backup 'WD5TB:backup/vzdump-lxc-300-2026_11_03-12_43_47.tar.zst'
300: 2026-11-22 01:06:16 INFO: removing backup 'WD5TB:backup/vzdump-lxc-300-2026_11_13-00_04_12.tar.zst'
300: 2026-11-22 01:07:01 INFO: removing backup 'WD5TB:backup/vzdump-lxc-300-2026_11_15-00_10_02.tar.zst'
300: 2026-11-22 01:07:28 INFO: pruned 3 backup(s) not covered by keep-retention policy

700: 2026-11-22 01:07:29 INFO: Starting Backup of VM 700 (lxc)
[truncated for brevity]
700: 2026-11-22 01:07:30 INFO: creating vzdump archive '/mnt/pve/WD5TB/dump/vzdump-lxc-700-2026_11_22-01_07_29.tar.zst'
[truncated for brevity]
700: 2026-11-22 01:36:58 INFO: prune older backups with retention: keep-monthly=1
700: 2026-11-22 01:36:58 INFO: removing backup 'WD5TB:backup/vzdump-lxc-700-2026_11_03-11_16_33.tar.zst'
700: 2026-11-22 01:37:07 INFO: removing backup 'WD5TB:backup/vzdump-lxc-700-2026_11_13-00_39_13.tar.zst'
700: 2026-11-22 01:37:12 INFO: removing backup 'WD5TB:backup/vzdump-lxc-700-2026_11_15-02_05_04.tar.zst'
700: 2026-11-22 01:37:15 INFO: pruned 3 backup(s) not covered by keep-retention policy

900: 2026-11-22 01:37:16 INFO: Starting Backup of VM 900 (qemu)
[truncated for brevity]
900: 2026-11-22 01:37:16 INFO: include disk 'sata0' 'local-lvm:vm-900-disk-1' 122108M
900: 2026-11-22 01:37:16 INFO: include disk 'efidisk0' 'local-lvm:vm-900-disk-0' 4M
900: 2026-11-22 01:37:16 INFO: creating vzdump archive '/mnt/pve/WD5TB/dump/vzdump-qemu-900-2026_11_22-01_37_16.vma.zst'
[truncated for brevity]
900: 2026-11-22 01:37:21 INFO:   0% (529.2 MiB of 119.2 GiB) in 3s, read: 176.4 MiB/s, write: 99.2 MiB/s
[truncated for brevity]
900: 2026-11-22 02:02:52 INFO: 100% (119.2 GiB of 119.2 GiB) in 25m 34s, read: 46.6 MiB/s, write: 45.9 MiB/s
[truncated for brevity]
900: 2026-11-22 02:02:54 INFO: prune older backups with retention: keep-monthly=1
900: 2026-11-22 02:02:54 INFO: removing backup 'WD5TB:backup/vzdump-qemu-900-2026_11_01-07_43_26.vma.zst'
900: 2026-11-22 02:03:03 INFO: removing backup 'WD5TB:backup/vzdump-qemu-900-2026_11_03-13_57_25.vma.zst'
900: 2026-11-22 02:03:09 INFO: removing backup 'WD5TB:backup/vzdump-qemu-900-2026_11_09-01_29_18.vma.zst'
900: 2026-11-22 02:03:15 INFO: removing backup 'WD5TB:backup/vzdump-qemu-900-2026_11_15-02_45_49.vma.zst'
900: 2026-11-22 02:03:21 INFO: pruned 4 backup(s) not covered by keep-retention policy
 
Last edited:
You can try the prune keep mechanism out here to get a better feeling for this: https://pbs.proxmox.com/docs/prune-simulator/index.html

A keep-weekly=1 will keep at most one and per week, nothing more. Which is then the most current one. Setting just a single setting and setting it just to 1 will always act the same as keep-last. I.e., at a prune for backups will keep the sum of all keep-X settings while deleting all others.

E.g. keep-last=1,keep-daily=1,keep-weekly=1 will at maximum keep three backups, i.e. the latest from each time window.

keep-last=1,keep-daily=1,keep-weekly=5 can keep up to five backups, but there might be also some get pruned from the current week until the job ran at least for 5 weeks, when it than can actually fulfill the keep-weekly=5.
 
Last edited: