Skip to content
Backups

Backups you never have to remember

Every MySQL, PostgreSQL and durable Valkey database is backed up daily and each backup kept 7 days unless you choose otherwise, stored away from the database itself. Your apps’ volumes get snapshots and backups too.

  • On by default
  • Your schedule: 6 h to weekly
  • Keep 1 to 35 days
  • Volume snapshots too
Backup schedule · orders-dbBack up now
  • Every 6 h
  • Every 12 h
  • Daily
  • Weekly
At07:30 IST
Keep each backup7 days (1–35)
  • 17 Oct, 07:30 IST1.4 GB · AutomaticCompleted
  • 16 Oct, 15:42 IST1.4 GB · ManualCompleted
Example screen.
Your safety net

Seven days back, one backup a day

By default a backup is taken every day at 07:30 IST, and each one is removed once it is older than your retention. Back up now adds one whenever you need it; those stay until you delete them.

orders-db · last 7 days7 of 7 completed
  1. Sat11 Oct07:30
  2. Sun12 Oct07:30
  3. Mon13 Oct07:30
  4. Tue14 Oct07:30
  5. Wed15 Oct07:30
  6. Thu16 Oct07:3015:42 manual
  7. Fri17 Oct07:30
Example screen.

How a restore works

  1. Pick a backup17 Oct, 07:30 IST · 1.4 GB
  2. A new databaseorders-db-restored · its own address
  3. Check itThe original keeps running
  4. SwitchPoint your app at the new address and deploy

Restore is for PostgreSQL and Valkey today, into the same engine and version; MySQL backups are taken, and restoring them is coming soon. Backups help you recover, but they aren’t a guarantee: check a restore before you rely on it.

Why it matters

The backup you need is the one that exists

Your problem

The backup script stopped weeks ago and nobody noticed.

On Drasken Cloud

Backups run on a schedule you can see, with every result, completed or failed, listed on the database’s Backups tab.

Your problem

You’re about to run a risky migration.

On Drasken Cloud

Select Back up now first. It’s listed straight away, marked Completed when it’s done, and kept until you delete it.

Your problem

Restoring over the live database is terrifying.

On Drasken Cloud

A restore always creates a new database. Check it, then point your app at it; the original keeps running.

What's included

Protection for databases and volumes

Your schedule

Every 6 or 12 hours, daily or weekly, at a time you choose.

Stored apart

Database backups are kept away from the database’s own storage.

Restore into a new database

PostgreSQL and Valkey today; MySQL coming soon.

Volume snapshots

Quick point-in-time copies of an app’s volume, kept on the volume’s own storage.

Volume backups

Copies of a volume’s snapshot, kept away from the volume’s storage.

Safe deletes

Deleting a database keeps its backups unless you choose to delete them too.

Details

Specifications

Databases
MySQL, PostgreSQL, Valkey (durable; a Valkey cache keeps nothing on disk and has no backups)
Default
Daily at 07:30 IST, each backup kept 7 days
Schedule
Every 6 h, 12 h, daily or weekly, at a time you choose
Retention
1 to 35 days; backups you take with Back up now stay until you delete them
Restore
Into a new database of the same engine and version (PostgreSQL, Valkey); MySQL coming soon
Volumes
Snapshots and backups, taken from the volume’s page; restoring them isn’t available yet
Pricing

Simple storage pricing

Backups and snapshots are charged for the storage they use, by the GB per month; each kind has its own rate.

How pricing works
Database backupsper GB stored
₹ — /mo
Volume snapshotsper GB stored
₹ — /mo
Volume backupsper GB stored
₹ — /mo
Questions

Questions about backups

  • Yes, for every MySQL, PostgreSQL and durable Valkey database: daily, each kept 7 days unless you change it. A Valkey cache keeps nothing on disk, so it has no backups.

Spend this week on your product, not your servers.

Create an account, add a project and deploy your first app.

  • Billed by the hour in rupees
  • Cancel any time
  • One GST invoice a month