Devpilot
Backups

Backups

Protect your databases, files, and server images with Devpilot backup plans — schedule them manually, on an interval, on cron, or in real time, and store them in any of seven destinations.

Devpilot's Backups area lets you define backup plans (what to back up, where to store it, how often, and how long to keep it), then runs those plans for you and keeps a detailed record of every run. Whether you need nightly database dumps, rolling file snapshots, or continuous real-time replication, Backups gives you a single place to configure and monitor it all.

What you can back up

Devpilot backup plans come in three types:

  • Database backups — capture one or more MySQL, PostgreSQL, MongoDB, or Redis databases.
  • File backups — capture one or more directories on a server, with support for exclude patterns and Docker volumes.
  • Image backups — capture full server or disk snapshots through your cloud provider.

Schedule modes

Each plan runs in one of four modes:

  • Manual — the plan only runs when you press Run now or trigger it via the API.
  • Interval — runs every N minutes, hours, days, or weeks.
  • Cron — runs on a cron expression in a timezone you choose.
  • Real-time — continuously streams changes (database CDC for MySQL/PostgreSQL, file-system watching for file plans). See Real-time backups for the full picture.

Where backups are stored

Each plan points at a destination: local disk, Amazon S3, Azure Blob, SFTP, Google Cloud Storage, Google Drive, or Cloudinary. Destinations are encrypted, reusable across plans, and testable from the UI before you commit to them.

Jump in

Backups live at the workspace level. Any plan, destination, or history you see is scoped to the workspace you're currently viewing.