From 0d7e13328364aac177a6215e1e0625d071deff02 Mon Sep 17 00:00:00 2001 From: Fizzlepoof Date: Tue, 26 May 2026 02:37:32 +0000 Subject: [PATCH] Document Serenity DB retirement after PD cutovers --- docs/planning/SERENITY_CLEANUP_WAVE_1.md | 25 ++++++++++++++++++++---- docs/servers/SERENITY.md | 2 ++ 2 files changed, 23 insertions(+), 4 deletions(-) diff --git a/docs/planning/SERENITY_CLEANUP_WAVE_1.md b/docs/planning/SERENITY_CLEANUP_WAVE_1.md index d129190..37e3880 100644 --- a/docs/planning/SERENITY_CLEANUP_WAVE_1.md +++ b/docs/planning/SERENITY_CLEANUP_WAVE_1.md @@ -56,12 +56,12 @@ Wave 1 explicitly excludes: ## Live facts this plan is based on -From the live Serenity audit: +From the live Serenity audit before D5/D6/D7: - ARR/torrent locality is still tied to `/mnt/user/data` -- `GameVault` points at local Postgres on `10.5.30.5:5432` -- `RomM` points at local MariaDB on `10.5.30.5:3306` -- live container env inspection still shows those explicit DB_HOST/DB_PORT bindings on 2026-05-25 +- `GameVault` pointed at local Postgres on `10.5.30.5:5432` +- `RomM` pointed at local MariaDB on `10.5.30.5:3306` +- live container env inspection showed those explicit DB_HOST/DB_PORT bindings on 2026-05-25 before cutover - quick live checks did not surface immediate DB dependencies for `Wizarr`, `Shelfmark`, or `Notifiarr` - `Newt` is still needed - legacy Pi-hole containers are still running even though Technitium is now the intended DNS path @@ -76,6 +76,8 @@ Live execution on 2026-05-25 established: - the recent non-running `Created` containers (`calibre-web`, `SuggestArr`, `Cleanuparr`, `calibre`, `agregarr`) were metadata-verified and then removed after confirming they were still only `Created`, had `restart=no`, and were not live workloads - `Unraid-Cloudflared-Tunnel` was audited, stopped, and removed after verification showed it was only transport-alive and no current public traffic depended on it - the Serenity Pi-hole HA stack (`binhex-official-pihole`, `pihole-serenity`, `unbound-pihole-serenity`, `keepalived-pihole-serenity`) was then stopped and removed after live mixed-host DNS checks confirmed the Technitium path remained healthy without it +- `gamevault` and `gamevault-db` validated healthy on PD, then Serenity `postgresql15` was exported, stopped, archived for rollback, and removed during D7 +- `romm` and `romm-db` validated healthy on PD, then Serenity `MariaDB-Official` was exported, stopped, archived for rollback, and removed during D7 ## Wave 1-A: legacy Pi-hole removal @@ -495,6 +497,21 @@ Definition of done: - Serenity-side DB appdata is retained for cooldown/rollback, not deleted immediately - docs and host inventory updated to show Serenity no longer carries those DB pairs +Execution notes (2026-05-25): +- PD validation passed before source retirement: + - `gamevault`, `gamevault-db`, `romm`, and `romm-db` all reported healthy + - HTTP checks returned `200` from PD for `http://127.0.0.1:8785/` and `http://127.0.0.1:8457/` + - PD DB quick checks returned 18 public tables for `gamevault` and 20 tables for `romm` +- Serenity rollback retention created at `/mnt/user/backups/doris/serenity-d7-db-retire-20260525-213531` + - `romm.sql` + - `gamevault.sql` + - `mariadb-official-appdata.tgz` + - `postgresql15-appdata.tgz` +- Serenity source DB appdata paths were intentionally left in place for cooldown: + - `/mnt/user/appdata/mariadb-official` + - `/mnt/cache/appdata/postgresql15` +- After D7, `docker ps -a` on Serenity no longer listed `MariaDB-Official` or `postgresql15` + ## Open item that still needs verification - `reranker` mounts `/mnt/user/appdate/reranker` diff --git a/docs/servers/SERENITY.md b/docs/servers/SERENITY.md index 6e35e7c..53a72c1 100644 --- a/docs/servers/SERENITY.md +++ b/docs/servers/SERENITY.md @@ -71,6 +71,8 @@ Serenity hosts the secondary backup Technitium node on `10.5.30.10`. - No GPU; reranker uses CPU-only TEI image - Tailscale active — reachable at `100.94.87.79` from any Tailscale node +- Local Serenity DB containers for the old GameVault and RomM stacks (`postgresql15` and `MariaDB-Official`) were retired on 2026-05-25 after both apps validated healthy on PD. +- Cooldown/rollback artifacts for that retirement were retained on Serenity under `/mnt/user/backups/doris/serenity-d7-db-retire-20260525-213531`, and the original DB appdata paths were left in place rather than deleted immediately. ## Planned future role