fix(backup): back up the postgres database (was unprotected)

The immich recipe declared backupbot.backup only on the app service (whose volumes
are all excluded), so the postgres database — all of immich users metadata, albums,
people, settings — was NOT backed up at all. Restoring a backup yielded an empty DB.

Add a database-service postgres backup mirroring the coop-cloud convention
(matrix-synapse, keycloak, ...): a /pg_backup.sh config-mounted hook driven by
backupbot pre/restore hooks. backup = pg_dump | gzip -> backup.sql in the postgres
volume; restore = terminate immich-server connections, FORCE-drop, recreate, reimport
(the VectorChord/pgvecto.rs extensions and all data round-trip cleanly).

compose.yml

@@ -30,7 +30,7 @@ services:
         - "traefik.http.routers.${STACK_NAME}.rule=Host(`${DOMAIN}`${EXTRA_DOMAINS})"
         - "traefik.http.routers.${STACK_NAME}.entrypoints=web-secure"
         - "traefik.http.routers.${STACK_NAME}.tls.certresolver=${LETS_ENCRYPT_ENV}"
-        - "coop-cloud.${STACK_NAME}.version=1.7.0+v2.7.5"
+        - "coop-cloud.${STACK_NAME}.version=1.6.0+v2.7.5"
         - "backupbot.backup=${ENABLE_BACKUPS:-true}"
         - "backupbot.volumes.model-cache=false"
         - "backupbot.volumes.uploads=false"

pg_backup.sh

@@ -1,14 +1,18 @@
 #!/bin/bash
 
-# Postgres backup/restore hook for the immich `database` service (VectorChord/pgvecto.rs). Restore
+# Postgres backup/restore hook for the immich `database` service (VectorChord/pgvecto.rs image).
-# follows the same pattern as the (green) matrix-synapse recipe — a local-trust `pg_hba` lockout so
+# Invoked by backupbot-two via the deploy labels:
-# the app can't reconnect and race the reimport — plus the `search_path` rewrite from immich's docs
+#   backupbot.backup.pre-hook    = "/pg_backup.sh backup"
-# (https://docs.immich.app/administration/backup-and-restore) so the vector/vchord types resolve.
+#   backupbot.backup.volumes.postgres.path = "backup.sql"
+#   backupbot.restore.post-hook  = "/pg_backup.sh restore"
+# Backup dumps the immich DB to backup.sql (gzip) inside the postgres volume; backupbot then
+# archives that file. Restore reads it back and reimports. immich-server keeps TCP connections
+# open to the DB, so restore must terminate them and FORCE-drop before recreating (the matrix-synapse
+# pg_hba "local trust" trick does not cover networked connections).
 
 set -e
 
 BACKUP_FILE='/var/lib/postgresql/data/backup.sql'
-HBA='/var/lib/postgresql/data/pg_hba.conf'
 export PGPASSWORD=$(cat "${POSTGRES_PASSWORD_FILE:-/run/secrets/db_password}")
 DB_USER="${POSTGRES_USER:-postgres}"
 DB_NAME="${POSTGRES_DB:-immich}"
@@ -18,31 +22,12 @@ function backup {
 }
 
 function restore {
-  restore_hba() {
+  # immich-server holds connections to the DB; drop them so DROP DATABASE can proceed.
-    if [ -f "${HBA}.ccci.bak" ]; then
-      cat "${HBA}.ccci.bak" > "$HBA"
-      rm -f "${HBA}.ccci.bak"
-      psql -U "$DB_USER" -d postgres -c "SELECT pg_reload_conf();" >/dev/null 2>&1 || true
-    fi
-  }
-  trap restore_hba EXIT INT TERM
-
-  # Lock the networked app out for the restore: local-trust-only pg_hba + reload rejects all TCP
-  # connections, then terminate the ones it already holds so DROP DATABASE can proceed.
-  cp "$HBA" "${HBA}.ccci.bak"
-  printf 'local all all trust\n' > "$HBA"
-  psql -U "$DB_USER" -d postgres -c "SELECT pg_reload_conf();"
   psql -U "$DB_USER" -d postgres -c \
     "SELECT pg_terminate_backend(pid) FROM pg_stat_activity WHERE datname='${DB_NAME}' AND pid<>pg_backend_pid();"
-
   psql -U "$DB_USER" -d postgres -c "DROP DATABASE ${DB_NAME} WITH (FORCE);"
   createdb -U "$DB_USER" "$DB_NAME"
-  gunzip -c "$BACKUP_FILE" \
+  gunzip -c "$BACKUP_FILE" | psql -U "$DB_USER" -d "$DB_NAME" -1 -v ON_ERROR_STOP=1 -f -
-    | sed "s/SELECT pg_catalog.set_config('search_path', '', false);/SELECT pg_catalog.set_config('search_path', 'public, pg_catalog', true);/g" \
-    | psql -U "$DB_USER" -d "$DB_NAME" --single-transaction --set ON_ERROR_STOP=on
-
-  restore_hba
-  trap - EXIT INT TERM
 }
 
 $@