Backup Runs
A backup run is a single execution of a backup policy.
Run Schema
| Field | Description |
|---|---|
id | Unique identifier |
policyId | Associated backup policy |
status | queued, running, succeeded, failed |
targetType | volume, database, or service-derived scope |
sizeBytes | Backup size |
artifactPath | Where the backup is stored |
startedAt | When the run started |
completedAt | When the run finished |
error | Error message (if failed) |
Triggering Runs
# Run a one-off backup from an existing policy
daoflow backup run --policy bkp_pol_123 --yes
# Run with JSON output
daoflow backup run --policy bkp_pol_123 --json --yes
Viewing Runs
# List recent backup runs
daoflow backup list --json
{
"ok": true,
"data": {
"runs": [
{
"id": "bkp_run_123",
"policyId": "bkp_pol_123",
"serviceName": "my-app",
"status": "succeeded",
"artifactPath": "backups/my-app/2026-03-15.tgz",
"bytesWritten": 52428800,
"finishedAt": "2026-03-15T02:15:00Z"
}
]
}
}
Failed Backups
Failed backups are first-class failures — they are visible in the UI, API, and CLI. They are never silently dropped.
{
"id": "bkp_run_789",
"status": "failed",
"error": "SSH connection timeout to server production-vps",
"startedAt": "2026-03-15T02:00:00Z"
}