docs(disk-gc): clarify GC schedule applies to PBS datastore only
PR Pipeline — Authorize → Validate → Review → Merge / auth (pull_request) Successful in 4s
PR Pipeline — Authorize → Validate → Review → Merge / validate (pull_request) Successful in 3s
PR Pipeline — Authorize → Validate → Review → Merge / lint (pull_request) Successful in 6s
PR Pipeline — Authorize → Validate → Review → Merge / ai-review (pull_request) Successful in 4s
PR Pipeline — Authorize → Validate → Review → Merge / gate (pull_request) Successful in 0s
PR Pipeline — Authorize → Validate → Review → Merge / auth (pull_request) Successful in 4s
PR Pipeline — Authorize → Validate → Review → Merge / validate (pull_request) Successful in 3s
PR Pipeline — Authorize → Validate → Review → Merge / lint (pull_request) Successful in 6s
PR Pipeline — Authorize → Validate → Review → Merge / ai-review (pull_request) Successful in 4s
PR Pipeline — Authorize → Validate → Review → Merge / gate (pull_request) Successful in 0s
The 20:00 UTC PBS GC cron (proxmox-backup-manager datastore prune) applies only to /tank/pbs-backup (pbs-datastore). It does NOT touch media volumes (/media/*) which are report-only at all threat levels. This clarification prevents the recurring confusion where a 96% media volume triggers a GC expectation, when the GC schedule never applies to it. Closes the 2026-09-17 correction: 'the GC schedule is now 20:00 UTC, protects the backup datastore, NOT the nearly-full media volume.'
This commit is contained in:
@@ -228,6 +228,14 @@ call summary-reporter
|
|||||||
plan: plan
|
plan: plan
|
||||||
```
|
```
|
||||||
|
|
||||||
|
## GC SCHEDULE (PBS datastore only)
|
||||||
|
|
||||||
|
The PBS GC schedule `0 20 * * *` (20:00 UTC) applies **only** to the PBS datastore
|
||||||
|
(`/tank/pbs-backup` on storepve), NOT to media volumes. Media volumes (/media/*) are
|
||||||
|
report-only at all threat levels. The cron job runs `proxmox-backup-manager datastore
|
||||||
|
prune --datastore storepve-datastore --keep-daily 35` which only affects the PBS
|
||||||
|
datastore; it does not touch media volumes or any other filesystem.
|
||||||
|
|
||||||
## GC Strategies by Host Type
|
## GC Strategies by Host Type
|
||||||
|
|
||||||
### Docker Hosts (kagentz 105, syslog-api 116, docker-vm 109, amdpve .15)
|
### Docker Hosts (kagentz 105, syslog-api 116, docker-vm 109, amdpve .15)
|
||||||
|
|||||||
Reference in New Issue
Block a user