Backups only count if they are recent, consistent, and realistically restorable.
- Confirm the scheduled weekly run completed.
- Confirm a fresh backup set exists under:
/mnt/backups/Backup/Appdata Backup/
- Confirm verification remains enabled in plugin settings.
- Check retention is still:
- 14 days
- keep minimum 4 backups
- Confirm the expected exclusions still match reality:
For each Duplicacy backup path, confirm:
- backup jobs succeeded
- prune jobs succeeded
- check jobs succeeded
- local storage path is reachable
- offsite B2 storage is reachable
- Appdata BackupSet → B2 Altair-Appdata-Backup
- Photos → local /backupdrive/Backup/Immich Backup
- Photos-B2 → B2 Altair-Photo-Backup
- Check the newest local appdata backup set exists.
- Check the most recent Duplicacy backup logs for errors.
- Confirm prune and check jobs are not silently failing.
- Spot-check B2 bucket accessibility if something looks off.
- Record meaningful failures or changes in the change logs.
A backup is not considered trustworthy just because a job says success.
Prefer one of these when making high-confidence claims:
- inspect resulting backup sets directly
- verify snapshot presence in Duplicacy
- perform a sample restore or at least a targeted dry inspection
Escalate immediately if:
- appdata plugin has no fresh weekly set
- Duplicacy photo backups fail
- B2 auth breaks
- retention behavior changes unexpectedly
- restore paths become ambiguous
Whenever the backup plan changes, update: