Skip to content
All services

Offsite, versioned and restore-tested

Automated WordPress backup system setup

A backup that has never been restored is a guess. Our automated WordPress backup system setup gives you scheduled, versioned copies of files and database stored offsite in S3 or Backblaze B2, encrypted, monitored, and proven with a real restore before we hand over. If the host fails or the site is hacked, you are back in minutes, not days.

  • S3 or Backblaze B2
  • Encrypted, write-only keys
  • Monitored every run

Three pillars of a real backup

What the setup includes

Scheduling, offsite storage, retention, encryption, monitoring and a documented restore, configured to match how often your site actually changes.

Get a quote
  1. 01

    Scheduled and incremental

    Database dumps hourly or daily and file backups incremental, so a large uploads folder is copied once and only changes move afterwards. WooCommerce stores get a frequency that matches how often orders arrive.

  2. 02

    Offsite, versioned, encrypted

    Copies go to Amazon S3 or Backblaze B2 in a separate account from the host, with versioning and lifecycle rules for retention, server-side encryption, and credentials that can write but never delete.

  3. 03

    Monitored and restore-tested

    Every run reports to a healthcheck endpoint, so a silent failure sends an alert instead of a surprise. We perform a full restore to staging before handover and document the steps for your team.

How an automated WordPress backup system setup works

Most WordPress owners believe they have backups. The host does “daily backups”, a plugin was installed years ago, and nobody has looked since. Then a plugin update corrupts wp_options, or a hacked theme file gets copied faithfully into every nightly snapshot for three weeks, and the restore either fails or restores the damage. An automated WordPress backup system setup is about removing the guesswork: a known schedule, a known location, a known retention policy, and a restore that has been performed at least once by someone who wrote down how.

Why host backups are not enough

  • They live on the same infrastructure. If the host has an outage, a billing dispute or a disk failure, the backup goes with the site.

  • Retention is short, often seven days. A hack discovered on day ten has no clean copy to go back to.

  • Nobody is alerted when a job fails. A cron that stopped in March is discovered in September.

  • Restores are all-or-nothing. You usually cannot pull a single table or the uploads from one day without restoring everything.

Host backups are a fine second layer. They should not be the only one.

The design we build

The system has four parts, and the tooling changes with the hosting:

  1. Database

    mysqldump --single-transaction --quick or wp db export on a schedule set by system cron, not WP-Cron, so it runs whether or not anyone visits the site. Frequency is hourly for stores and membership sites, daily for content sites. Dumps are gzipped and named with a timestamp.

    system crongzip
  2. Files

    Incremental copies of wp-content with restic or rclone, which deduplicate at block level so a 20 GB uploads folder does not cost 20 GB per day. Core and plugin files are included because a restore should not depend on the WordPress.org mirror being reachable.

    resticrclone
  3. Offsite storage

    Amazon S3 with bucket versioning and Object Lock, or Backblaze B2, always in an account you own and separate from the hosting account. Lifecycle rules keep hourly copies for two days, dailies for 30, weeklies for six months and monthlies for a year, or whatever retention your compliance needs dictate.

    S3 Object LockB2
  4. Least-privilege credentials Most important

    An IAM policy that allows s3:PutObject and s3:GetObject but not s3:DeleteObject, so a compromised server cannot wipe its own history. This is the single most important detail and the one most plugin setups skip.

    PutObjectDeleteObject

On managed hosts without shell access we use UpdraftPlus or BlogVault against the same remote storage rules; on a VPS or an AWS build we prefer restic with a systemd timer, because it gives snapshots, encryption and pruning in one tool. If you are moving hosts anyway, backups are wired in as part of an AWS hosting migration for WordPress so the new server is protected from day one.

Monitoring and alerts

Every job ends by pinging a Healthchecks.io or CloudWatch endpoint. If the ping does not arrive on schedule, you and we get an email or Slack message. We also record backup size per run: a sudden drop usually means a directory was excluded by mistake, and a sudden jump often means the cache directory was included or a malware payload landed. A weekly summary lists successful runs, current storage use and the date of the last restore test.

The restore drill

Before handover we restore the latest backup to a staging site, run wp core verify-checksums and wp plugin verify-checksums --all, log in, and check a recent order or post. The procedure is written as a checklist with the exact commands. We recommend repeating it quarterly and can do it for you under website maintenance and support. A clean, dated backup is also the fastest route to recovery after a compromise; our hacked WordPress site recovery work always starts by asking whether one exists.

Timeline and what we need

A typical automated WordPress backup system setup is complete in two to three working days: half a day for the storage account and policies, a day for the jobs and monitoring, and the rest for the restore drill and documentation. It is a fixed price agreed in writing, and the only recurring cost is storage, billed directly by S3 or B2.

What we need from you

  • SSH or SFTP access
  • Database credentials
  • An AWS or Backblaze account, or permission to create one in your name

We need SSH or SFTP access, database credentials, and either an AWS or Backblaze account or permission to create one in your name. Read our guide to offsite, versioned and actually tested WordPress backups for the reasoning behind each choice, then tell us about your site and you will have a scope and a fixed quote within 24 hours.

Three steps, one handover

How the engagement runs

Step 1

Assess what needs protecting

We measure the database and uploads size, how often content and orders change, what the host already provides and any compliance retention rules, then send a written plan and a fixed price.

Step 2

Build the jobs and storage

Storage account, versioning and least-privilege credentials first, then the scheduled database and file jobs with monitoring. Everything is tested on a first full run and a second incremental run.

Step 3

Restore, document, hand over

A full restore to staging proves the backups work. You receive the runbook, alert setup and credentials, plus the option of quarterly restore drills under a maintenance plan.

Estimated cost

What an automated backup setup costs

Typical starting prices in US dollars. Every site is different, so you get an exact fixed quote after a free first look, usually within 24 hours.

  • Backup setup

    from$99

    Daily automated backups of files and database, set up properly.

    • Daily schedule
    • Database and files
    • Failure alerts
  • Recommended

    Offsite and restore-tested

    from$149

    Encrypted, versioned copies offsite, with a real restore test.

    • Everything in the setup
    • S3 or B2 offsite, versioned
    • Restore tested on staging
  • Up to 5 sites

    from$299

    The offsite setup rolled out across your sites.

    • Everything in offsite
    • Up to 5 WordPress sites
    • One monitoring dashboard

Estimates, not a checkout. The final price depends on your site's size and setup. You approve the quote before any work starts.

Questions we get asked about WordPress backups

Something not covered here? Tell us about your site and hosting.

Start a discussion

How much does an automated WordPress backup system setup cost?

Setup starts at an estimated $99, or $149 with encrypted offsite copies and a tested restore, and $299 for up to five sites. Ongoing storage in S3 or Backblaze B2 is billed by the provider directly and depends on retention length and the size of your uploads folder.

How often should my site be backed up?

Match the schedule to how often data changes. A WooCommerce or membership site should have hourly database backups so at most an hour of orders is at risk. A content site updated weekly is fine with daily. File backups run daily in both cases because incremental copies are cheap.

Can you back up a site on shared or managed hosting?

Yes. Without shell access we configure UpdraftPlus or BlogVault to push to your own S3 or B2 bucket with the same versioning and write-only credentials. The trade-off is that plugin backups rely on WordPress itself being healthy, so external monitoring matters even more there.

What happens if a backup job fails?

Every run pings a monitoring endpoint on completion. A missed ping triggers an email or Slack alert to you and to us, so the failure is known the same day rather than at restore time. Backup sizes are logged too, so a run that succeeds but copies far less than usual is flagged as well.

Ready to know your backups actually work?

Tell us where the site is hosted and how often it changes. Within 24 hours you will have a backup plan, the storage estimate and a fixed quote for the setup, including a proven restore before we hand it over.

Start a discussion