Incomplete snapshots without metadata show 0 bytes in backup data totals #62

New Issue

parkel · 2026-05-23T01:32:54+02:00

parkel commented

2026-05-23 01:32:54 +02:00

Problem

The dashboard and host cards can show 0 bytes for incomplete snapshot data even when incomplete snapshot records/directories exist. This likely happens when incomplete snapshot records were discovered from disk or created before storage metadata was recorded, so the SQL metadata has no stats.storage.snapshot.allocated_size_bytes value.

Expected

Incomplete backup data totals should be useful for operators:

Prefer recorded snapshot metadata when available.
Fall back to measuring the snapshot path on disk when metadata is missing and the path is locally readable.
Keep missing/unreadable paths safe and non-fatal.
Cover host-level and dashboard-wide totals with tests.

Scope

This is a bugfix for the backup data totals introduced in #53.

## Problem The dashboard and host cards can show `0 bytes` for incomplete snapshot data even when incomplete snapshot records/directories exist. This likely happens when incomplete snapshot records were discovered from disk or created before storage metadata was recorded, so the SQL metadata has no `stats.storage.snapshot.allocated_size_bytes` value. ## Expected Incomplete backup data totals should be useful for operators: - Prefer recorded snapshot metadata when available. - Fall back to measuring the snapshot path on disk when metadata is missing and the path is locally readable. - Keep missing/unreadable paths safe and non-fatal. - Cover host-level and dashboard-wide totals with tests. ## Scope This is a bugfix for the backup data totals introduced in #53.

parkel added this to the 1.2 milestone 2026-05-23 01:32:54 +02:00

parkel referenced this issue from a commit

2026-05-23 01:36:04 +02:00

## Summary

parkel referenced a pull request that will close this issue

2026-05-23 01:36:14 +02:00

## Summary #63

parkel closed this issue

2026-05-23 01:36:18 +02:00

Sign in to join this conversation.