Skip to main content

Website Backup & Recovery

A backup only counts if you can restore from it

Many businesses discover their backups are incomplete, stored on the same server or never restorable at the moment they need them. We design, run and regularly test backups so recovery is a procedure, not a hope.

Restore test passedOff-site copy synced

Business impact

Why backups fail when they are needed most

Backups are usually set up once and forgotten. Recovery depends on details that only show up during a real incident: what was included, where it was stored and how long a restore really takes.

Ransomware and hacks reach on-server backups

Backups kept on the same server or account as the website can be encrypted, deleted or infected along with it. Off-site, access-separated copies are essential.

Retention too short to help

If malware or a bad change goes unnoticed for weeks, a backup set that only keeps a few days of history will only contain the problem.

Recovery time affects revenue

How long a restore takes matters as much as whether it works. Knowing your realistic recovery time lets you plan around it rather than discover it during an outage.

Common issues

Problems we regularly solve

Database missing from the backup

File-only backups that capture the website code but not the database where content, orders and users actually live.

Backups stored next to the site

Archives kept in the web root or on the same hosting account, sometimes publicly downloadable and always lost if the server fails.

Silent backup failures

Jobs that started failing after a disk filled up, a credential changed or a plugin updated, with no one alerted.

Restores never tested

Archives that are corrupt, incomplete or depend on server configuration nobody documented, discovered only during an emergency.

Retention that does not match risk

One daily copy overwritten each night, so a problem noticed two days later cannot be undone.

No one knows the restore procedure

The person who set up the backups has left, and there is no written runbook explaining how to bring the site back.

What's covered

What's included in website backup & recovery

Our backup and recovery service is designed around two questions: how much data can you afford to lose (your RPO) and how quickly do you need to be back online (your RTO). It follows the widely used 3-2-1 principle of multiple copies on separate storage with at least one off-site.

Backup design

Agreeing what is backed up – files, databases, media, configuration – how often, and for how long, based on how frequently your site changes.

Off-site, separated storage

Encrypted backups stored with a separate provider or account from your hosting, with access controls that limit who can delete them.

Monitoring and alerting

Every backup job is checked for success, size and completeness, and failures are investigated rather than ignored.

Scheduled test restores

Restoring backups to an isolated environment on a schedule and confirming the site works, following our backup restore test checklist.

Recovery runbook

A written, site-specific procedure for restoring service, including access, order of steps, DNS considerations and who to contact.

Incident recovery

Hands-on restoration after failed updates, data loss, hosting failures or compromise, coordinated with malware removal where needed.

Maintenance activities

What we do, and how often

Exact frequencies depend on your plan and platform. This is a typical schedule.

Daily

  • Automated file and database backups
  • Backup job success and size checks

Weekly

  • Review of backup retention and storage usage
  • Investigation of any failed or unusually small backups

Monthly

  • Backup status summary in your maintenance report
  • Check that new databases, sites or directories are included

Quarterly

  • Full test restore to an isolated environment
  • Measured restore time recorded against your RTO
  • Runbook review and update

On demand

  • Pre-change backup before major updates or migrations
  • Incident restore

Our methodology

How we work

01

Define recovery objectives

We agree how much data loss and downtime your business can tolerate, which drives backup frequency, retention and storage choices.

02

Implement and separate

Backups are configured for files and databases, encrypted and sent to storage separate from your hosting account.

03

Verify by restoring

We restore backups to an isolated environment and check the site works, rather than relying on job logs alone.

04

Document and rehearse

A recovery runbook is written from the test restores, so the steps are proven and anyone on the team can follow them.

Business benefits

What you gain

Proven restores

Regular test restores give evidence that recovery works, along with a realistic estimate of how long it takes.

Protection from shared failure

Separated, off-site storage helps ensure a hosting failure or compromise does not take your backups with it.

Recovery anyone can follow

A tested runbook removes dependence on one person's memory.

Evidence for insurers and auditors

Backup reports and restore records help demonstrate your continuity arrangements when asked.

Technologies supported

  • Amazon S3
  • S3-compatible object storage
  • Object Lock / immutable storage
  • restic
  • rsync
  • mysqldump
  • Percona XtraBackup
  • JetBackup
  • UpdraftPlus
  • Cron
  • GPG encryption

Running something not listed? Ask us – we'll tell you honestly if it's a fit.

Who it's for

Who needs website backup & recovery?

Online stores

Businesses whose orders and customer data change constantly and cannot be recreated by hand.

Regulated organisations

Healthcare, financial and education organisations that need documented backup and recovery controls. We support the technical controls but do not provide legal or compliance advice.

Businesses relying on host backups

Organisations who assume their hosting provider's backups are enough without knowing what is kept or how to restore it.

Industry guidance: E-commerce · Healthcare · Financial Services

FAQs

Website Backup & Recovery: common questions

My host already takes backups. Why do I need this?
Host backups are useful but often limited: short retention, stored in the same infrastructure, restore only on request and no testing. We treat them as an extra layer, not the only one. Our article on why website backups often fail explains the common gaps.
How often should my website be backed up?
It depends on how often your data changes. A brochure site may need daily backups; a busy store may need much more frequent database backups. See how often a website should be backed up.
Where are backups stored, and who can access them?
In encrypted, off-site storage separate from your hosting, with access limited to named SupportSafe engineers and, if you wish, your own team. We can use storage in a region you specify.
How do you test that backups work?
We restore a recent backup to an isolated environment, check that pages, admin login and key functions work, confirm the database is complete and record how long the restore took.
What happens in an emergency restore?
We follow the site's runbook, agree with you which restore point to use, and restore to the live environment or a new one. If the cause was a compromise, we make sure the vulnerability is closed before bringing the site back online.
Can you back up sites you do not otherwise maintain?
Yes. Backup and recovery can be provided as a standalone service, though it works best alongside regular website maintenance.

Find out if your backups would actually work

Our free website health check includes a review of your current backup setup, where copies are stored and whether a restore has ever been tested.