docs(recovery): fix CNPG restore-test drill for the plugin-based barman

Conversation 1 Commits 1 Files Changed 1

+29 -7

1 Commits

Author	SHA1	Message	Date
claude-botandClaude Opus 4.8	6274dd66fb	docs(recovery): fix CNPG restore-test drill for the plugin-based barman ci/woodpecker/pr/pr-review Pipeline was successful Details The restore-test drill in RECOVERY.md told you to omit spec.plugins from the throwaway cluster ('NO spec.plugins / isWALArchiver here'). With the plugin-based barman this homelab now uses (barmancloud.cnpg.io ObjectStore + the barman-cloud.cloudnative-pg.io plugin), that is invalid: the instance manager can't load the plugin it needs to replay WAL during restore and dies at startup with 'Unknown plugin: barman-cloud.cloudnative-pg.io' — the cluster never becomes healthy. A real cold-rebuild DR following this drill would have failed the same way. Found + fixed by running the drill against im-pg on 2026-07-25 (restore succeeded once the plugin was declared; 33316 rows in 'asset', 584 MB DB). - Declare the barman plugin in spec.plugins with isWALArchiver: false — loaded so it can READ WAL for the restore, but never archives (stays read-only against the backup path). Update the intro prose to match. - Verification: pg_stat_user_tables n_live_tup reads 0 right after a restore (stats not gathered), so that view is not a data check — add pg_database_size and note counting a real table instead. - Teardown: the old 'reclaim the released PV afterwards' was too vague and leaks the Retain PV's RBD image (issue #262). Give the explicit recipe: capture the PV name, delete the cluster, then patch the released PV to Delete so the CSI reclaims the RBD image. The in-place cold-rebuild section (which keeps the live cluster's existing spec.plugins isWALArchiver: true) was already correct and is unchanged. Co-Authored-By: Claude Bot <claude-bot@renner.uno> Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-07-25 09:11:51 +02:00

Author

SHA1

Message

Date

claude-botandClaude Opus 4.8

6274dd66fb

docs(recovery): fix CNPG restore-test drill for the plugin-based barman

ci/woodpecker/pr/pr-review Pipeline was successful

Details

The restore-test drill in RECOVERY.md told you to omit spec.plugins from the
throwaway cluster ('NO spec.plugins / isWALArchiver here'). With the plugin-based
barman this homelab now uses (barmancloud.cnpg.io ObjectStore + the
barman-cloud.cloudnative-pg.io plugin), that is invalid: the instance manager
can't load the plugin it needs to replay WAL during restore and dies at startup
with 'Unknown plugin: barman-cloud.cloudnative-pg.io' — the cluster never becomes
healthy. A real cold-rebuild DR following this drill would have failed the same
way. Found + fixed by running the drill against im-pg on 2026-07-25 (restore
succeeded once the plugin was declared; 33316 rows in 'asset', 584 MB DB).

- Declare the barman plugin in spec.plugins with isWALArchiver: false — loaded so
  it can READ WAL for the restore, but never archives (stays read-only against
  the backup path). Update the intro prose to match.
- Verification: pg_stat_user_tables n_live_tup reads 0 right after a restore
  (stats not gathered), so that view is not a data check — add pg_database_size
  and note counting a real table instead.
- Teardown: the old 'reclaim the released PV afterwards' was too vague and leaks
  the Retain PV's RBD image (issue #262). Give the explicit recipe: capture the
  PV name, delete the cluster, then patch the released PV to Delete so the CSI
  reclaims the RBD image.

The in-place cold-rebuild section (which keeps the live cluster's existing
spec.plugins isWALArchiver: true) was already correct and is unchanged.

Co-Authored-By: Claude Bot <claude-bot@renner.uno>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-07-25 09:11:51 +02:00

docs(recovery): fix CNPG restore-test drill for the plugin-based barman #404