Public: anyone can read this; the crew can change it.

Backups leave the platform: one last copy of the 36 GB Forgejo dump, the lanes retired one by one, and a restore that never touches it #8949

Closed opened this has it

Landed in pull #9060 · run

opened this

forgejo-dump is suspended and 36 GB. The backup namespace's CronJobs are lanes the forge reads (FORGE_BACKUP_LANES, docs/features/backup-truth.md). The forge's own snapshot goes to its primary and a B2 mirror and does not need the platform.

Done when:

Files: docs/features/backup-truth.md, docs/SNAPSHOT.md, docs/RESTORE.md

Part of #7667 (inventory: docs/PLATFORM.md). Nothing is turned off by this issue without the owner present; the forge stays up throughout.

2 earlier comments
commented

Reviewed pull #9060 at its head: left open: Decide with the owner: does the dump's content come into the forge through the migrate flow (Forgejo repositories) so the dump is redundant, or is one copy kept in B2 / on the owner's disk. Written here. — A recommendation is written, but the owner's answer is still marked pending.; Each lane in FORGE_BACKUP_LANES has a line: what it backs up, who reads it after spin-down, or retired. — Only primary and mirror have rows; the backup/<name> rows are blank.; A restore drill from the bucket onto the box (the box issue) with the platform unreachable from it. — The steps are written; the drill has not been run.; The backup tile stays green throughout. — Nothing here touches the tile, and no evidence shows it staying green through a retirement or drill..

commented

Left open after pull #9060 landed: 4 unticked items remain (Decide with the owner: does the dump's content come into the forge through the migrate flow (Forgejo repositories) so the dump is redundant, or is one copy kept in B2 / on the owner's disk. Written here.; Each lane in FORGE_BACKUP_LANES has a line: what it backs up, who reads it after spin-down, or retired.; A restore drill from the bucket onto the box (the box issue) with the platform unreachable from it.; …). The planner files each as its own issue and closes this one; a person may close it, tick what is done, or say what is left. Until then the crew does not pick it again.

commented

Split. Pull #9060 shipped the work; the open boxes go like this:

  • Each lane has a line → #9067: the line lives with the lane in FORGE_BACKUP_LANES and shows on /settings/backups, the Resilience dialog and MCP backups; a retired lane stops being read, so the tile stays green through a retirement (the fourth box).
  • The dump decision is the owner's, not a builder's: @trevato, the recommendation is written in docs/RESTORE.md — bring the Forgejo repositories in through the migrate flow, or keep one copy in B2 / on your disk. Say which here or on #7667.
  • The drill from the bucket onto the box with the platform unreachable is a run on the box, by a person: bun scripts/restore-drill.ts (docs/RESTORE.md). The backup tile already turns red when the newest drill failed or did not run, so it reminds by itself.
Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs