# Back up and restore Docker data

> Create, download, restore, rename, and delete backups of Docker persistent volumes.

The service-level **Backups** tab protects the Docker service's persistent volumes. Container filesystem changes that are not stored on a persistent volume should be treated as disposable.

## Create a backup

1. Open **Dashboard → Services → your Docker service → Backups**.
2. Click **Create Backup**.
3. Add an optional name.
4. Confirm once and wait for **Completed**.

Only one active backup workflow can run at a time. The dashboard shows manual quota and retry state.

## Download or rename

Download a completed backup for an offline copy. Keep the tab open while large downloads are prepared. You can rename manual backups; automatic backups keep their generated name. A rename does not change the backup UUID.

## Restore

Restoring replaces current persistent-volume data.

1. Stop or quiesce applications that write continuously when practical.
2. Select a completed backup and click **Restore**.
3. Enable **Create safety restore point** to preserve current data.
4. Click **Restore Now**.
5. Wait until the service restore operation finishes before using app controls.
6. Start or redeploy the app only if required, then test its state.

Without a safety restore point, changes since the selected backup may be unrecoverable.

## Delete

Backup deletion is permanent. Confirm another usable copy exists first. If the node is offline, existing downloads may remain available, but create, restore, and delete actions are disabled.

## What is not covered

A volume backup is not a substitute for storing source code in version control, pinning images, recording environment configuration, or using application-native database exports. Keep those recovery materials separately.

See [Troubleshoot a Docker app](/docker/troubleshooting/) if a restored app does not start.