Skip to content

Compute decommission queue

Completed June 2026 execution record from the compute disposition review (owner decisions 2026-06-23, with later dated decisions below). Done records the original owner/disposition outcome, not current backup availability or recovery acceptance. This is not a new destroy queue.

Historical IDs and archive locations

Original local paths below identify created artifacts, not retained copies. VMID 102 was later reused for PostgreSQL (inventory record 2026-08-09). Do not restart, restore over or destroy a guest using this table as identity proof. Fresh guest identity and owner approval are required before any future operation.


Queue

Priority Host VMID Recorded owner gate Backup provenance Recorded destroy
1 k6-loadtest 105 Done 2026-06-24 Deleted 2026-06-24 (agent error); original prox:/var/lib/vz/dump/vzdump-lxc-105-2026_06_23-18_28_49.tar.zst destroyed
2 netboot.xyz 122 Done 2026-06-24 Last-recorded relocated 2026-06-24; original prox:/var/lib/vz/dump/vzdump-lxc-122-2026_06_23-18_32_33.tar.zst → infra-backups/dump/vzdump-lxc-122-2026_06_23-18_32_33.tar.zst destroyed
3 unmanic 103 Done 2026-06-24 Last-recorded relocated 2026-06-24; original prox:/var/lib/vz/dump/vzdump-lxc-103-2026_06_23-18_37_39.tar.zst → infra-backups/dump/vzdump-lxc-103-2026_06_23-18_37_39.tar.zst destroyed
4 aiproject 102 Done 2026-06-24 Deleted 2026-06-24 (agent error); original prox:/var/lib/vz/dump/vzdump-lxc-102-2026_06_23-18_43_17.tar.zst destroyed
5 caddy 117 Done 2026-06-24 Last-recorded relocated 2026-06-24; original prox:/var/lib/vz/dump/vzdump-lxc-117-2026_06_23-18_47_55.tar.zst → infra-backups/dump/vzdump-lxc-117-2026_06_23-18_47_55.tar.zst destroyed
6 dnsproject 107 Done 2026-06-24 (backup-before-destroy) Deleted 2026-06-24 (agent error); original prox:/var/lib/vz/dump/vzdump-qemu-107-2026_06_23-18_57_55.vma.zst destroyed
7 penpot 121 Done 2026-06-24 (no backup) Omitted by owner decision destroyed
8 reactive-resume 118 Done 2026-06-24 (no backup) Omitted by owner decision destroyed
9 metrimon 106 Done 2026-06-24 Failed twice (prox local full); no successful vzdump recorded; discovery export destroyed
10 nfs-monitoring 114 Done 2026-06-24 Recorded manual archive (native vzdump failed); infra-backups/dump/manual-lxc-114-rootfs-2026_06_24.tar.zst (~53 GB) + lxc-114-pct.conf destroyed
11 influxdb 111 Done 2026-06-24 Recorded archive; infra-backups/influx-lxc-111-2026-06-24/ (~7.8 GB) destroyed
12 sqlserver2022 110 Done 2026-06-25 Recorded vzdump; infra-backups/dump/vzdump-lxc-110-2026_06_25-19_13_03.tar.zst (5.18 GiB) destroyed

Provenance and recovery gates

The 2026-06-24 storage update records the surviving dumps for 122 netboot, 103 unmanic and 117 caddy moved from prox local to infra-backups/dump/. The original filenames above are kept; the destination paths combine those filenames with that recorded directory, not a new NAS listing. At that time the storage mount was /mnt/pve/infra-backups, on Whrrr export 192.168.6.215:/volume6/infra-backups.

The deletion incident records loss of the three local artifacts for 105, 102 and 107. Deleted, omitted, failed, recorded archive, and last-recorded relocated are separate outcomes. The metrimon discovery export is configuration evidence, not a recoverable disk backup. A completed destroy row does not prove recoverability.

No archive, NAS or alternate copy was inspected for this correction; it does not establish that no other copy exists. Before recovery, obtain owner authorization for a fresh recovery inventory, verify guest identity, archive availability and a trusted checksum, then perform an isolated restore with integrity and rollback checks. All of those recovery gates remain pending.

Backup patterns (historical context, not authorization)

Method When
Proxmox vzdump Any VM/LXC — vzdump <vmid> --storage infra-backups on prox (NFS 192.168.6.215:/volume6/infra-backups)
restic via backup-client If guest path is in tier-2/3 policy (most LXCs are not today)
Manual tar Small LXCs: mount rootfs or SSH + tar czf to Whrrr/infra-services

Store artifacts under Whrrr longterm or infra-services backup staging; reference path in commit message when marking inventory retired.

dnsproject (107): Owner 2026-06-24 clarified backup-before-destroy — full vzdump required even though original queue row had no explicit owner gate.


After destroy

Historical workflow only; this completed queue does not authorize new operations.

  1. Set status: retired in inventory/hosts/<id>.yaml; remove proxmox block if VMID gone.
  2. python scripts/proxmox-scan.py --write-baseline
  3. Run all render-* generators; commit.