backup-setup

name	backup-setup
description	Set up automatic vault backups to a synced folder or a cloud provider, with verified archives and tiered retention. Use when the user says 'back up my vault', 'set up backups', 'where are my backups going', or asks about losing their notes. Not for restoring or testing a restore (`backup-restore`); not for a one-off backup right now (`backup-now`).
integration	{"id":"vault-backup","name":"Vault Backup","mcp_server":null,"auth":"none"}

Backup Setup

Set up (or change) automatic backups of the whole vault: notes, projects, people, tasks, settings, and the vault's own version history. Runs on a schedule in the background, keeps a sensible ladder of older copies, and tells you loudly if it ever stops working.

What a backup contains

Every run writes a set of three files, stamped with the date and time:

File	What it is
dex-vault-<stamp>.tar.gz	The whole vault as one compressed archive
dex-vault-<stamp>.bundle	The vault's version history, individually verified so a restore is provable rather than hoped for
dex-vault-<stamp>.sha256	Fingerprints of both, so damage in storage is detectable

Secrets are deliberately left out: the .env file holding AI keys, generated tool configuration that can reference credentials, saved sign-in tokens (*token.json), the System/credentials folder, any .key or .pem file, virtual environments, and caches. Never store those in a synced folder. Keys live in the system keychain or get re-entered on restore. See for what a full rebuild needs beyond these files.