Reference

Backups & Migration

Backup/restore, per-profile export, whole-instance migration, and upgrades.

Backup & restore

./deploy/backup.sh            # /var/backups/aios/aios-<stamp>.tar.gz (keeps 14)
./deploy/restore.sh <archive> # stops services, safety-snapshots current
                              # state, restores, restarts

Everything that matters lives in /root/.aios — one archive is a full recovery point. Cron it nightly. The license signing key (/root/.aios-license-keys/) deserves its own off-server copy.

Self-service per-profile export (no root/SSH needed)

The backup above is whole-server and needs root. For exporting just one profile’s data — the thing a managed-hosting customer without shell access can actually do themselves:

POST /api/profile/backup?profile=<name>          # builds a tar.gz server-side
GET  /api/profile/backup                          # list built archives
GET  /api/profile/backup/download?filename=<name> # fetch one
POST /api/profile/restore?profile=<name>          # raw tar.gz bytes as the body

Note

No dashboard page for this yet (API only). Credentials (.env, credentials_pool.json) are excluded by default — pass include_credentials=true to the POST /api/profile/backup call if you need them in the export. Bound by the app’s 25MB body-size cap; a profile with a very large sessions.db can’t round-trip through this route yet — use the whole-server backup above for those.

Migrating a whole instance

To move everything (every profile, kanban, credentials, hooks) to a different machine — or to bootstrap a brand-new machine from an existing instance’s data, standing in for aios setup:

aios migrate export --out ~/aios-backup.aiosmig    # or: --github owner/repo
aios migrate import --from ~/aios-backup.aiosmig --home ~/.aios
                                                     # or: --github owner/repo@tag

Always encrypted (ChaCha20-Poly1305, passphrase-derived key) — you’re prompted for a passphrase if you don’t pass --passphrase or set AIOS_MIGRATE_PASSPHRASE (the prompt isn’t hidden yet, it’ll echo as you type). A wrong passphrase or a corrupted archive fails loudly rather than silently producing garbage. import refuses to touch a destination that already has data unless you pass --force — but works exactly as well against an empty or nonexistent --home, which is what makes it double as a fresh-install path. The --github target uploads/downloads the encrypted archive as a Release asset via the gh CLI (needs gh auth login done on both ends) — use a private repo, since the encryption protects the contents but not the fact that a release exists.

Unlike the per-profile export above, credentials are included by default here — the whole point of a migration is a working replacement instance.

Upgrades

Install the new release’s binaries, then re-run provision.sh (idempotent — it refreshes units and binaries without touching config/data), then ./deploy/e2e.sh <apex> to verify. Take a backup first.