> ## Documentation Index
> Fetch the complete documentation index at: https://docs.monk.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Back up and restore

> Run the snapshot and restore actions your database provides, with your approval each time

Many managed databases come with backup actions, such as taking a snapshot, listing backups or restoring. Monk can run those actions for you. You approve each one.

## Before you start

* A database that Monk manages. See [Add a database](https://docs.monk.io/guides/add-a-database.md).
* Backup actions exist for AWS RDS, MongoDB Atlas, Google Cloud SQL and DigitalOcean managed databases.
* Support also depends on the tier. For example, MongoDB Atlas exposes backups on dedicated clusters (M10 and up) but not on the free tier.

## Ask Monk

Find out what your database can do:

```
/monk which backup actions does my database have?
```

Then ask for one:

```
/monk take a snapshot of the database before I run the migration
/monk list the database backups
/monk restore the database from the latest snapshot
```

Monk lists the actions the database's integration declares and only runs one that exists. It won't invent arguments the action doesn't accept.

## What you review

Each action opens an approval in the [local dashboard](https://docs.monk.io/getting-started/local-dashboard.md) with the exact action and arguments. A restore can overwrite data, so read it carefully.

You can choose to always allow a specific action on a specific workload, for example listing backups. You can revoke that later:

```
/monk which actions have I always allowed?
```

Monk cannot tell from an action's name whether it only reads or also writes. Keep "always allow" for actions you know are safe.

## What you get

The action's output, such as a snapshot ID, a list of backups or the status of a restore job.

## Self-hosted databases

A database running as a container on your cluster has no backup action unless its template provides one. Use the database's own tools (for example `pg_dump` or `mongodump`) and your cloud's volume snapshots.

## Provider backups

Managed services run their own scheduled backups, configured in the provider's account. Check each provider's documentation for retention and restore options. The [integrations catalog](https://monk.io/integrations) lists the actions each integration declares.

## Next

* [Add a database](https://docs.monk.io/guides/add-a-database.md)
* [Move clouds](https://docs.monk.io/guides/move-clouds.md)
* [Services and data](https://docs.monk.io/concepts/services-and-data.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.