rake db:dump writes under /data, so running it first lets the dump ride the existing file backup. New phase shows up in the backup phases panel automatically.

Assisted-by: GLM-5.3 via pi

diff --git a/lotus-land-story/templates/backup.sh b/lotus-land-story/templates/backup.sh
index 76ef5b0..82c1e0b 100644
--- a/lotus-land-story/templates/backup.sh
+++ b/lotus-land-story/templates/backup.sh
@@ -95,6 +95,10 @@ ping_healthcheck /start
 # which blocks every later prune. unlock only removes stale locks.
 phase unlock restic unlock
 
+# Runs before the files phase so the dump it writes under /data is included
+# in the file backup.
+phase pro-tacts docker exec pro-tacts rake db:dump
+
 # A file-level copy of the running cluster isn't restorable; the postgres
 # phase's pg_dumpall is. The glob also covers the postgresql-15 path the
 # bookworm upgrade moves to.