Appearance
Off-site backup record (Hyper Backup)
DH-12, issue #297. This is a record of the Synology Hyper Backup job that copies NAS data off-site, kept in the repo so a buyer, or a restore after losing the NAS (docs/plans/deploy-hardening.md, "Losing the NAS"), does not depend on anyone's memory. It is read-only: nothing here changes the job.
Separate from this, infra/nas/backup/getmy-books-backup encrypts each nightly database dump and copies it to a Cloudflare R2 bucket in the EU (35-day lifecycle, ADR 0026). That path is recorded in the script. This page covers the Hyper Backup job only.
The owner fills every field marked TODO(owner) from the P2 read-only check (plan slice 2, "Before 2a merges"). Counts, names, ages and sizes only, no contents. Do not guess a value: leave TODO(owner) if it has not been seen.
| Field | Value |
|---|---|
| Job name | TODO(owner) |
| Checked on, and by | TODO(owner) |
| Shared folders in scope | TODO(owner) |
Is homes/deploy in scope? (yes or no) | TODO(owner) |
Is /volume1/backups/getmy-books in scope? (yes or no) | TODO(owner) |
| Is the registry data (image signatures) in scope? (yes or no) | TODO(owner) |
| Is the Postgres volume in scope? (yes or no) | TODO(owner) |
| Destination type and provider (no credentials) | TODO(owner) |
| Is it encrypted, and where is the key kept? (no key here) | TODO(owner) |
| Schedule | TODO(owner) |
| Retention (versions kept, rotation) | TODO(owner) |
| Last successful run, and its size | TODO(owner) |
| Last restore of a file from it, and when | TODO(owner) |
| Does Hyper Backup alert on failure, and to whom? | TODO(owner) |
If homes/deploy is in scope
Today's full-prd release .env files (the deploy SSH key, the owner DATABASE_URL) are then in off-site retention. The key rotation (plan 1d) and the W3 password rotations become mandatory, and the retention of those versions is a question for the Product Owner. Record the decision here: TODO(owner).
Same note for the encryption key
The dumps hold Xero and Starling tokens encrypted with XERO_TOKEN_ENCRYPTION_KEY, which sits in the release .env on the same volume. If both the dumps and homes/deploy are in scope, the off-site copy holds both (plan, "Backups and restore"). Record whether they are: see the rows above.