# Backup capacity and essentials assessment

The user asked how much space is needed and whether Nextcloud can hold only
essentials. Live aggregate sizing shows package blobs dominate at 4.45 GiB;
Git repositories are 480 MiB and the last SQL export 93 MiB before compression.
The existing 18-full-copy retention target needs 96.35 GB of Forgejo archive
storage alone, so it cannot fit the 10 GiB account. Its Sunday upload duplicates
that day's bytes under a weekly name.

Prepared `docs/backup-storage-tiers.md`: plan 125–150 GB for the current Forgejo
full-archive retention on Scaleway, separately budget native database/WAL and
other services, and target a 600 MiB essentials generation on Nextcloud. A
provisional 7-daily/2-weekly policy plus incoming overlap, other-service reserves
and headroom fits 10 GiB only after measured acceptance. No compressed essentials
artifact or total platform capacity is claimed as measured.

The reduced profile retains source/history, collaboration database, unique
attachments/LFS and recovery configuration; bulk packages require primary
coverage and an explicit rebuildability/bootstrap audit first. A primary-independent
essentials restore and separate owner retention executor are required before
cutover. This is folded into WP-0038-T04 instead of another overlapping workplan.
Live backup scope and retained good copies are unchanged.