Skip to main content
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.
  • Backup support depends on the service and 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:
Then ask for one:
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 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 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 lists the actions each integration declares.

​
Next