← All docs

Backups

DotDeployer backs up your PostgreSQL and SQL Server databases and sends them to object storage you own — your own S3 or DigitalOcean Spaces bucket. DotDeployer never stores a copy of your data itself.

Steps:

  1. Go to Settings → Object storage and add the S3 or DigitalOcean Spaces bucket you want backups sent to, along with its access credentials. They’re encrypted before they’re stored, the same as a provider token or an environment variable.
  2. On a server’s Databases tab, pick the bucket for a database and choose “Backup now”.
  3. The backup runs as a job and lands in the bucket you connected. Automatic scheduled backups and retention are not running yet — backups happen when you ask for them.

Restoring: because backups land in your own bucket in a standard format, restoring is a normal PostgreSQL or SQL Server restore from that file — there’s no DotDeployer-specific restore step or lock-in to a particular tool.

Why your own bucket: DotDeployer’s job is the control plane, not a place to store your customers’ data. Keeping backups in a bucket you own means you keep them, with the retention and region you choose, even if you ever cancel DotDeployer.

Object storage credentials: manage the bucket connection itself from Settings → Object storage; which databases back up to it is set per database on the server’s Databases tab.

The DotDeployer server Databases tab with a database ready to back up