A senior operator arrives at an incident and asks one question: “do we have a recent database backup or a recent filesystem backup, and are they from the same moment?” The answer determines what kind of recovery is even possible.
What’s happening
WordPress state is split across two stores that drift at very different rates:
- The database (
wp_posts,wp_options,wp_users, plugin tables) — changes continuously. Every published post, every WooCommerce order, every login, every plugin transient writes here. The right cadence is hourly or finer on transactional sites. - The filesystem (
wp-content/uploads, plugin and theme code, mu-plugins, custom drop-ins) — changes only when content is uploaded or code is deployed. On a well-managed site, deploys happen weekly; uploads happen continuously but the individual files are large and immutable once written.
Backing up both on the same cadence either over-backs-up the filesystem (expensive, slow, mostly redundant data) or under-backs-up the database (recovery point is too far back to be useful for transactional workloads).
The two failure modes:
- Database-only backup, filesystem lost — the site renders correctly but every uploaded image is broken. For a content site, every article without a hero image. For WooCommerce, every product without a photo.
- Filesystem-only backup, database lost — the uploads are intact but every post, comment, order, and user account is gone. WordPress boots into the installer.
Either alone is not a backup of the site.
How to verify
Two checks that answer “what do we actually have”:
# 1. Identify the timestamp of the most recent database dump
ls -la /backup/<account>/databases/wp_acmewp.sql.gz
mysqldump --version # confirm the dump tool matches the source
# 2. Identify the timestamp of the most recent uploads archive
ls -la /backup/<account>/homedir/wp-content/uploads/
If the two timestamps are more than 24 hours apart on a transactional site, the next restore will be inconsistent — the database will reference uploads that don’t exist, or vice versa.
The fix
The cadence we run on managed WordPress, by workload type:
- Editorial / publisher site — full backup (DB + FS) nightly. Database-only point-in-time every 4 hours during the editorial day. Uploads change rate is low; nightly is sufficient.
- WooCommerce / transactional site — database-only every 15 to 30 minutes via binary log replication or Percona xtrabackup incremental. Full backup nightly. Uploads change rate is moderate but bounded; nightly catches it.
- Membership / SaaS-on-WP site — database every 15 minutes minimum. Filesystem nightly with deploy-triggered snapshots on every release.
The cadence question is workload-specific. The constraint that holds across all three: the database backup and the filesystem backup must reference timestamps the recovery team can reason about together.
Stack Harbor matches backup cadence to workload type as part of environment management. If your current cadence was inherited rather than designed, book a backup review.