# Your backup command reference.

> Find CalmBackup commands for running backups, listing snapshots, checking status and restoring data. Use an explicit configuration for isolated recovery tests.

Canonical page: https://www.calmbackup.com/docs/commands

Run backups, list snapshots, inspect status and restore with an explicit configuration.

[All guides](https://www.calmbackup.com/docs)

Commands

Run a backup

```
calmbackup run
```

List backups

```
calmbackup list
```

Restore a backup

```
calmbackup restore <backup-id>
```

Check status

```
calmbackup status
```

Global flags

| --config <path> | Override config file location |
| --- | --- |
| --verbose, -v | Verbose output |
| --quiet, -q | Suppress non-error output (useful for cron) |

## Use an explicit recovery configuration

The restore command writes to the database and directory paths in the configuration it loads. For a practice restore, use a separate machine or isolated environment and review every destination first.

```
calmbackup --config /path/to/recovery.yaml restore &lt;backup-id&gt;
```

**Restores can overwrite existing data.**

PostgreSQL restores use clean/if-exists behavior, MySQL imports SQL, and SQLite replaces the configured database file. Included directories are copied to configured paths. Do not use your production configuration for a rehearsal.

## What the command does

The client obtains backup metadata, uses a matching local cache or downloads the encrypted archive, authenticates and decrypts it, extracts the data, and invokes the database restore. Application validation remains a separate step.

[Read the complete recovery workflow →](https://www.calmbackup.com/recovery)
