Skip to content

armgit / Pulse

Public Imported from GitHub
0

Real-time monitoring dashboard for Proxmox VE, PBS, Docker, Kubernetes, TrueNAS and vSphere. Self-hosted, with alerts for failed backups, full disks, unhealthy containers and offline nodes.

Compose archive-kind safety with current backup retention guidance

pulse-triage[bot]c571c086ef55
diff --cc docs/release-control/v6/internal/subsystems/storage-recovery.md
index e7f850365f,0ff56c8cd8..6c0524c4b9
--- a/docs/release-control/v6/internal/subsystems/storage-recovery.md
+++ b/docs/release-control/v6/internal/subsystems/storage-recovery.md
@@@ -21,25 -21,40 +21,59 @@@
## Purpose
+### Backup retention never substitutes for verification
+
+The existing restore-point State cell and drawer status prioritise running or
+failed completion and then the reported verification result. A point kept when
+pruning still says Unverified or Verified as reported. Retention without a
+verification verdict says Kept with an informational tone, never Protected.
+The existing detail names Prune protection separately and says Not reported
+when backup verification is unavailable. Guest snapshots retain their existing
+informational state. The shared Coverage evidence uses the same state wording.
+Canonical workload protection, freshness, policy and inventory counts are not
+inferred from prune retention or an individual verified file.
+
+The normal-suite `backupRetentionPresentation.test.tsx` exercises the real
+inventory consumer, independent assessment, explicit/missing verification,
+search compatibility and same-point polling with an open drawer and focus.
+Shared badge and drawer tests retain completion precedence and reactive tones.
+Desktop/narrow consuming browser proof checks the existing rows and details.
+No provider data, route, access, retention operation or guest recovery changes.
+
+ ### Retained local archives do not change kind when a VMID is reused
+
+ A PVE VM archive cannot advance the backup date or protect a live LXC using
+ the same connection and VMID, and an LXC archive cannot protect a replacement
+ VM. Local guest-date selection groups explicit `qemu`/`vm` and `lxc`/`ct`
+ subjects independently before comparing recency. Incomplete archives still
+ supply no completion date. Existing best-effort matching of legacy/untyped
+ rows, PBS matching, task state and provider observation policy are unchanged.
+
+ Recovery mapping uses the explicit artifact kind. When it contradicts the
+ live guest lookup, the archive retains its historical typed canonical subject
+ without borrowing the new occupant's ID or display name. Collector placement
+ lookup likewise ignores an opposite-kind occupant: its archive keeps the read
+ node, while a same-kind migrated guest still supplies its actual placement.
+ The final state-layer alignment uses the same typed fence, so publishing
+ the list cannot undo the collector decision. Both date and placement selection
+ share the model's explicit-kind normalisation; legacy/untyped fallback remains
+ unchanged. The independent local storage read origin and archive ID are unchanged.
+ Same-kind metadata and legacy/untyped fallback retain their existing behaviour.
+ The point ID, archive time, size and public JSON shape do not change. Ordinary
+ collection updates existing point attribution; no deletion, schema migration,
+ backup/restore or guest-agent operation is introduced.
+
+ `TestUpdateStorageBackupsForInstanceKeepsArchiveGuestKind`,
+ `TestSyncGuestBackupTimesLocalArchiveGuestKinds`,
+ `TestFromPVEStorageBackupsRetainsExplicitGuestKind` and the normal-suite
+ `TestPVEArchiveSubjectKindLifecycle` cover both replacement directions, aliases,
+ connection isolation, migrated placement/read origin, recency, incomplete files,
+ legacy controls, retained raw
+ artifacts, canonical dates/subjects, partial reads, complete absence and ordinary
+ recovery. Actual lifecycle frames drive production Coverage and backup-status
+ browser proof at desktop and narrow widths. This is a source safety repair,
+ not #3248 causal attribution, native recovery or verified restore availability.
+
### Archive guest kinds come from artifact discriminators
PVE archive type detection ignores the storage-name prefix and incidental