# Backups

URL: /docs/backups

Source: https://github.com/easypanel-io/monorepo/blob/main/apps/website/content/docs/backups/index.mdx

Protect databases and persistent volume data with external backups.



Easypanel can send database dumps and App or Box volume data to a configured
storage provider. Database and volume backups have different formats, retention
behavior, and recovery workflows, so choose the guide that matches the data you
need to protect.

<Cards>
  <Card href="/docs/backups/database" title="Database Backups" description="Schedule, run, retain, and restore logical database backups" />

  <Card href="/docs/backups/volumes" title="Volume Backups" description="Mirror App and Box volume mounts to external storage" />
</Cards>

## Configure a destination [#configure-a-destination]

Open the server's **Settings**, select **Storage Providers**, and add a
destination before creating a backup configuration. See
[Storage Providers](/docs/storage-providers) for setup, permissions, and
connection testing. Easypanel supports:

* [Local storage](/docs/storage-providers/local);
* [FTP and SFTP](/docs/storage-providers/ftp-sftp);
* [Dropbox](/docs/storage-providers/dropbox) and
  [Google Drive](/docs/storage-providers/google-drive);
* [Amazon S3 and S3-compatible providers](/docs/storage-providers/s3),
  including Cloudflare R2, DigitalOcean Spaces, Backblaze B2, and Wasabi.

Use a remote destination for disaster recovery. A local provider on the same
server will not protect data from a server or disk failure.

Give each backup configuration its own destination path. This prevents one
configuration's retention or sync behavior from affecting unrelated files.

## Build a recoverable backup plan [#build-a-recoverable-backup-plan]

A scheduled job is useful only when its output can be restored. For every
important service:

1. Keep the destination outside the Easypanel server.
2. Run the backup manually after creating or changing its configuration.
3. Check the backup action log and confirm that the expected object exists at
   the provider.
4. Test recovery into non-production data.
5. Monitor future runs and destination capacity.

For applications such as WordPress, protect both parts of the application:
create a logical backup of the database service and separately protect uploaded
files stored in a volume.

<Callout type="warn">
  Removing a backup configuration removes its schedule from Easypanel. It does
  not remove files already stored at the destination. Manage those files and any
  provider-side lifecycle rules separately.
</Callout>