Skip to main content
Live. This area is documented as current, user-reliable behavior.

​
Goal

Recover WordPress deliberately, with both the files and the database accounted for.

​
Prerequisites

  • A deployed WordPress site

​
Workflow

1
Before risky WordPress changes, take a WordPress (stack) backup for the files and a managed-database backup for the MySQL data — together, so they match.
2
To recover, restore the stack backup (files) and the managed-database backup (data) from completed backups.
3
Validate the public site, admin access, media, and plugin behavior after restore.

​
Files and database are backed up separately

A native WordPress site has two stores: the WordPress files in a persistent volume (wp-content — themes, plugins, uploads), and a separate managed MySQL database. The WordPress backup archives the file volume to S3; it does not include the database. The database is a managed database resource with its own backup and restore flow.
  • WordPress (stack) backup → the wp-content file volume.
  • Managed-database backup → the MySQL data.
  • A consistent recovery point needs both, taken close together.

​
Restore, then validate

  • Restore the file backup and the database backup from completed backups — restoring only one leaves the site inconsistent.
  • After restore, check the public site, admin login, media/uploads, and plugin behavior.
  • Treat the restore status as “data is back”, not “the application is verified” — confirm the site yourself.

​
Back up before risky changes

Run both backups before core updates, major plugin or theme changes, or migrations. That gives you a known-good point — files and database in sync — to restore to if an update breaks the site.

​
Expected result

You can recover a WordPress site fully, with files and database restored to a consistent point.

​
Common failures

  • Backing up the files but forgetting the managed database (or vice versa), so the restore is inconsistent.
  • S3 backup storage is not configured for the environment, so backups cannot be created.
  • Restoring from an incomplete backup, or assuming a green badge means the app is correct without checking the site.

Back up and restore a database

Use durable recovery storage correctly and understand why backups are independent from portable SQL transfers.

Back up and restore a stack

Use S3-backed named-volume archives to protect and recover stateful stack data.

WordPress Control Surface

A first-class operational surface for direct WordPress projects: overview, narrow safe actions, diagnostics, and recent history.