Feature • Backups & restore

Backups to your own storage. Restore in one click.

Rubuz takes encrypted Restic snapshots of your databases, app volumes and config on a schedule, and sends them to your own S3-compatible bucket. Restore onto the same server or a fresh one.

Start Free Trial → See how backups work

Encrypted with Restic Your own S3-compatible bucket Scheduled snapshots One-click restore Monthly restore tests

backup-engine // restic s3:https://s3.eu-central-1.wasabisys.com/rubuz-backups

Scheduled: Daily at 02:00 UTC

Total Data Protected

142.8 GB

Across 8 apps & 4 databases

S3 Bucket Storage Used

16.4 GB

Encrypted with Restic

Last Snapshot

Complete

Uploaded to your bucket

Restore

1-Click

Same server or a new one

Snapshot ID	Contents	Uploaded	Duration	Status
#snp-a9f82d01 (latest)	Databases, volumes, config	+142 MB (encrypted)	48s	✓ Complete
#snp-e73b18c4	Scheduled (daily)	+86 MB (encrypted)	41s	✓ Complete
#snp-3c220f19	Scheduled (daily)	+18 MB (encrypted)	39s	✓ Complete

01 // Before and after

A backup on the same server is not a backup. Send it somewhere else.

Backups usually fail quietly: a dump that sits on the disk it protects, or a script that stopped working months ago.

✕ Hand-rolled backup scripts

The usual setup

✕
Backups on the same disk: A dump in a local folder is gone the moment the server is.
✕
Plain files in a bucket: An unencrypted dump uploaded by a script can be read by anyone who gets the bucket keys.
✕
Cron jobs that fail quietly: A script breaks after an update and nobody notices until the day you need it.
✕
Database only: You get the SQL back, but the uploaded files in your volumes and the app's config are missing.

With Rubuz

✓ Restic + your bucket

Backups with Rubuz

✓
Off the server, in your storage: Snapshots go to your own S3-compatible bucket, so losing the server does not mean losing the data.
✓
Encrypted with Restic: Every snapshot is encrypted before it leaves your server.
✓
On a schedule: Pick a schedule once and Rubuz takes the snapshots for you.
✓
Everything comes back together: Databases, volumes and config restore in one click, on the same server or a fresh one.
✓
Restore-tested every month: Rubuz restores your database dumps into throwaway databases once a month, and for any backup you ask about, so you know it works before you need it.

02 // What you get

What gets backed up, and where it goes.

Databases, files and config, encrypted and sent to storage you own.

Pillar 01

Scheduled snapshots

Pick a schedule once. Rubuz takes the snapshots and sends them straight from your server to your S3-compatible bucket.

On every run:

• Databases, volumes and config

• Encrypted before upload

• Sent to your own bucket

Pillar 02

Encrypted with Restic

Snapshots are encrypted with Restic before they leave your server, so the files in your bucket cannot be read without the key.

With Restic:

• Encryption before upload

• An open-source backup format

• Snapshots you can list and restore

Pillar 03

Databases, volumes and config

A backup is more than a SQL file. Rubuz captures each database, each app's volumes and the config that ties them together.

Covered:

• Each app's /data directory and volumes

• Postgres, MySQL, Mongo and Valkey

• App config

Pillar 04

One-click restore, even on a new server

Restore a snapshot in one click. If the server is gone, connect a fresh one and restore onto it.

Restore to:

• The same server

• A fresh Debian or Ubuntu server

• From any snapshot in your bucket

03 // Your storage

Use the S3-compatible storage you already have.

Snapshots go from your server to your own bucket. The storage account is yours, so the backups are too.

Amazon S3 AWS

Cloudflare R2 Cloudflare

Wasabi Cloud S3-compatible

Backblaze B2 S3-compatible

DO Spaces DigitalOcean

MinIO / Custom Self-Hosted

🔒

Your bucket, your account: Snapshots are encrypted with Restic on your server and land in storage you control.

No lock-in

Need more than one server?

Rubuz also runs managed Kubernetes in your own DigitalOcean, Vultr or Linode account, with high availability, autoscaling and rolling deploys, from the same console as your servers.

Compare plans

04 // Questions

Questions about backups on Rubuz.

What does a backup include? ↓

Your databases (Postgres, MySQL, Mongo and Valkey), each app's volumes including its persistent /data directory, and the app config.

Can I restore onto a new server or a different provider? ↓

Yes. Connect a fresh server running Debian 13 or Ubuntu 26.04 LTS from any VPS provider and restore the snapshot onto it in one click. Databases, volumes, /data and config come back together.

Which storage providers can I use? ↓

Any S3-compatible storage, including Amazon S3, Cloudflare R2, Wasabi, Backblaze B2, DigitalOcean Spaces and MinIO.

Where are my backups stored? ↓

In your own bucket. Snapshots are encrypted on your server and sent to the storage you connect, so the files live in your account.

How do I know a backup will restore? ↓

Rubuz tests it. Once a month, and whenever you ask from a backup's row, it replays that backup's database dumps into throwaway databases and checks what they hold. The result is kept on the backup, and you get an alert if a test fails.

Backups and restore

Back up to your own bucket. Restore when you need it.

Connect a server and an S3-compatible bucket, pick a schedule, and your apps are backed up.

Start free trial →

✓ No card needed • 14-day free trial