root/Jyotisha
1
0
Fork 0
Code Issues 42 Pull Requests Actions Packages Projects Releases Wiki Activity

fix(release): daily backups no longer replace the recovery point

Browse Source 
Product chose to keep the scheduled backup, but the current recovery point must stay the one created by hand. Daily runs still encrypt and restore-verify, then record a separate latest-backup note.

Co-Authored-By: Grok (agent loop)
This commit is contained in:
jesse-ux
2026-10-15 16:16:48 +08:00
co-authored by Grok (agent loop)
parent 6ba63470a9
commit 5c0d895391
7 changed files with 349 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/operations/production-release-runbook-20261014.md
+2
View File
@@ -39,6 +39,8 @@ Gitea → Create Production Recovery Point。Use workflow from：`main`。`deplo
通过：成功结束，记下三样东西：`recovery_reference`、`recovery_created_at`、以及它已经写明还原验证通过。主机上的 `/opt/jyotisha-production/.state/recovery-baseline.env` 里必须有 `RECOVERY_FORMAT=2`。没有这一行，或者数字小于 2，都不要往下走：先再点一次创建恢复点。8 月以来不带权限的旧备份不能再拿来回退。加密备份在生产主机的备份目录里，不要打开、不要把密钥贴出来。
每日自动备份不是这一步的恢复点。它每天只把加密文件存档并做还原核对，不会改 `recovery-baseline.env`。隔夜的自动备份不会换掉你上线前手动建的恢复点。上线前仍然要点 Create production recovery。
失败：停。不要迁移。
## 5. 在主机上演练迁移