Common signs: no backups, untested backups or backups on the same server. Usual causes: backups never set up or never restored. What we do: automate encrypted off-site backups and test a restore. What you get: proof you can recover.
Our backup and restore setup makes sure you can get your data back after a mistake, failure or attack. A Codersarts engineer sets up automated, encrypted backups of your database and files, stores them away from your servers, sets retention rules, and tests a full restore so you know it works. Fixed price from $29 with 24h delivery.
Backup & Restore at a Glance
Item | Details |
|---|---|
Starting price | $29 for a backup health check |
Delivery | 24 hours for a check, 1 day for setup |
Databases | PostgreSQL, MySQL, MongoDB, Supabase, SQL Server |
Storage | S3-compatible storage such as AWS S3, Hetzner Storage Box or Backblaze B2 |
Includes | Encryption, retention rules, alerts and a tested restore |
What you get | Backups and proof you can recover |
Revisions | One revision round included |
What Is a Tested Backup?
A tested backup is one you have actually restored and checked, not just one that a script says it created. Good backups are automatic, encrypted, stored away from the servers they protect, kept for a defined period, and restored regularly to prove recovery works within the time your business can accept.
Signs Your Backups Need Work
You're not sure when the last backup ran
Backups are stored on the same server as the database
Nobody has ever tried restoring one
You rely only on your hosting provider's snapshots
Uploaded files aren't backed up at all
Why Backups Fail When You Need Them
Never tested
Backups run but are corrupt or incomplete.
Same location
A server failure or attack destroys the data and the backups together.
Files forgotten
The database is backed up but user uploads aren't.
No alerts
Backups silently stop and nobody notices for months.
Quick Checks You Can Try First
Find the date of your latest backup and where it's stored.
Check that uploads and files are included, not just the database.
Make sure at least one copy is stored outside your server or provider account.
Try restoring last night's backup to a test database.
If the problem remains, our engineers take it from there.
How We Set Up Backups
Review. We check what data exists and how it's backed up today.
Automate. We schedule database and file backups.
Encrypt and store. We encrypt backups and store them off-site.
Retention. We set daily, weekly and monthly retention rules.
Alert. We alert you if a backup fails or is missing.
Test restore. We restore to a test environment and verify the data.
What You Get
Automated database and file backups
Encrypted off-site storage
Retention rules and failure alerts
A tested restore with recovery time measured
A short restore runbook
Example result (illustrative)
A college platform kept database backups on the same Hetzner server. We moved encrypted daily backups to a separate storage box, added file backups for uploads, and ran a test restore in 18 minutes. The team now has a runbook and alerts if any backup fails.
What Is Included and Not Included
Included | Not included |
|---|---|
One database and its file storage | Many databases (priced per database) |
Encryption, retention and alerts | Storage costs |
One tested restore | Full disaster recovery across regions (higher package) |
Restore runbook | Ongoing restore drills (available with prepaid hours) |
Pricing for Backup & Restore
Package | Best for | Starting at | Delivery |
|---|---|---|---|
Backup health check | Review current backups and gaps | $29 | 24 hours |
Backup setup | Automated, encrypted, off-site backups plus a tested restore | $199 | 1 day |
Disaster recovery plan | Recovery targets, failover and restore drills | $599 | 3 days |
You get a fixed quote after we review your setup. You approve the scope before any payment.
Who This Is For
Startups that have never tested a restore
Apps on a single VPS or server
Teams handling customer, student or payment data
Companies preparing for SOC 2 or ISO 27001
What We Need From You
Server or database access
Where uploads and files are stored
How much data loss and downtime is acceptable
Access to storage for backups
Code and data privacy
We sign an NDA on request, work with the least access needed, and never keep copies of your data after delivery. You own all code, configuration and notes.
Key Terms Explained
RPO: recovery point objective, how much recent data you can afford to lose
RTO: recovery time objective, how long recovery may take
Off-site backup: a copy stored away from the main servers
Point-in-time recovery: restoring a database to an exact moment
Common Mistakes We Avoid
Never testing a restore
Storing backups on the same server
Backing up the database but not uploaded files
Keeping backups unencrypted
Need More Than One Task?
Need full disaster recovery and replication? See Replication & Backup. Or use Prepaid Developer Hours to cover several tasks from one prepaid balance.
Related Tasks
Uptime Monitoring & Alerts Setup to catch failures early
Hetzner Server Setup with backups included
Move localStorage Data to Database so data is backed up at all
Frequently Asked Questions
How often should I back up my database?
At least daily for most apps, with point-in-time recovery for apps where losing a day of data isn't acceptable.
Are my hosting provider's snapshots enough?
They help, but keep at least one encrypted copy outside the provider account and test restores.
How long should backups be kept?
A common pattern is 7 daily, 4 weekly and 3 to 12 monthly copies, depending on your needs and regulations.
Can you back up Supabase?
Yes. We set up scheduled exports in addition to Supabase's own backups.
Make Sure You Can Recover
Share your database and hosting details, and a Codersarts engineer will set up backups and prove a restore works.