Backup & Restore
Persistent data is a core feature in DaoFlow. The backup system supports database dumps, volume archives, and S3-compatible remote storage.
When DAOFLOW_ENABLE_TEMPORAL=true, both scheduled backups and one-off backup run executions are
dispatched through Temporal. The operator backup surfaces expose the backing workflow ID so you can
jump directly into Temporal Web when a run needs deeper diagnosis.
When Temporal mode is disabled, one-off backup requests fail fast instead of being silently queued
without an execution engine behind them. Enable DAOFLOW_ENABLE_TEMPORAL=true before relying on
manual backup run operations.
Overview
| Feature | Description |
|---|---|
| Policies | Define what to backup, when, and retention rules |
| Runs | View backup execution history |
| Restore | Restore from a specific backup |
| S3 Storage | Configure remote backup storage |
Backup Types
| Type | What It Captures |
|---|---|
| Database dump | Logical dump of PostgreSQL databases |
| Volume archive | Tar archive of Docker named volumes |
| Compose package | Full service state including config and volumes |
Quick Start
# Run a manual backup
daoflow backup run --policy bkp_pol_123 --yes
# List recent backups
daoflow backup list --json
# Restore from a backup
daoflow backup restore --backup-run-id bkp_run_123 --yes
Permissions
| Action | Required Scope |
|---|---|
| View policies | backup:read |
| View backup history | backup:read |
| Preview restore | backup:read |
| Run a backup | backup:run |
| Restore a backup | backup:restore |