Setup Automated Database Backup to Cloud

The Problem

A backup that lives on the same server as the database it's backing up isn't really a backup — if that server goes down or gets compromised, you lose both the original and the copy.

About this problem

A backup stored on the same server as the database it protects isn't really protecting against the scenarios that matter most — if that server fails, gets compromised, or is accidentally wiped, the backup disappears along with the original. Off-server storage is what actually makes a backup meaningful rather than theoretical.

This comes up for anyone running a production database who's realised their current backup (if any) wouldn't survive the server itself going down.

What's Included

• A backup script/job tailored to your database engine
• Automatic upload to cloud storage (S3-compatible or similar) after each run
• Retention policy so old backups don't pile up and cost more than they should
• A real restore test to confirm the backups are actually usable

What's NOT Included

• Ongoing cloud storage costs — billed by your storage provider
• Backing up file storage as well, unless included
• Disaster recovery planning beyond the backup itself

How It Works

1. Build a backup job tailored to the specific database engine in use (mysqldump, pg_dump, or similar).
2. Configure automatic upload to cloud storage (S3-compatible or similar) immediately after each backup run.
3. Set a retention policy so old backups are cleaned up automatically rather than accumulating storage costs indefinitely.
4. Schedule the job to run reliably via cron at your chosen frequency.
5. Perform a real restore test from the cloud-stored backup to confirm it's genuinely usable.

In practice: you buy the service, send over whatever access or details the job needs, I investigate and do the work, and you confirm it's resolved before we call it done.

Frequently Asked Questions

Why isn't a local database backup enough?

If the server itself fails, is compromised, or is wiped, a backup stored only locally is lost along with the original data — off-server storage protects against exactly that scenario.

What cloud storage works for automated database backups?

Any S3-compatible storage (AWS S3, Backblaze B2, DigitalOcean Spaces, etc.) works well and is usually inexpensive for backup-sized data volumes.

How much does cloud backup storage typically cost?

For most small-to-medium databases, a few pounds a month at most — exact cost depends on backup size, retention length, and the provider chosen, billed directly by them.

How do I know my cloud backups would actually work if needed?

Through a real restore test from the cloud-stored file, which is part of setting this up properly rather than assuming the upload succeeding means the backup is valid.

Can this back up more than just the database?

This service is scoped to database backups specifically; backing up file storage as well can be added if needed, but isn't assumed by default.

What happens to old backups in cloud storage?

A retention policy automatically removes backups past a certain age, keeping storage costs predictable rather than growing indefinitely.