Backup Scope
Identify whether the current backup covers files, database tables, uploads, plugin data, WooCommerce orders, and configuration. A database-only backup and a files-only backup protect different risks.
Resource
A recovery-readiness checklist for backup scope, restore ownership, retention, local versus off-site risk, approvals, communication, and post-restore verification.
Problem, cause, fix, verify
Problem
A backup is not a recovery plan until the team knows what it contains, where it lives, who may restore it, and what business data could be overwritten.
Audience
WordPress administrators, agencies, and business owners responsible for recovering a site after a failed update, migration, malware cleanup, hosting issue, or data mistake.
First check
Identify whether the current backup covers files, database tables, uploads, plugin data, WooCommerce orders, and configuration. A database-only backup and a files-only backup protect different risks.
Verify
Review this disaster recovery checklist whenever hosting, payment flows, membership features, backup storage, or agency ownership changes. Recovery plans become stale when the site architecture changes faster than the documentation.
Editorial trust
On this page
Resource Use
For: WordPress administrators, agencies, and business owners responsible for recovering a site after a failed update, migration, malware cleanup, hosting issue, or data mistake.
Checklist Flow
Identify whether the current backup covers files, database tables, uploads, plugin data, WooCommerce orders, and configuration. A database-only backup and a files-only backup protect different risks.
Name the person who can approve restore work and the person who can execute it. During an outage, unclear authority is often as damaging as a missing archive.
Record how many restore points exist, how old they are, whether they are local or off-site, and whether any backup artifacts are publicly reachable.
A safe restore rehearsal should verify login, public pages, forms, checkout, search visibility, and key plugin workflows. Keep the result with the maintenance record.
Backup & Restore Manager can support deliberate local backup and restore review. Use cloud-managed recovery language only when the paid workflow is actually connected and authorized.
Write down who tells customers, editors, clients, or store staff that recovery work is happening. A clear message should name the affected workflow, expected verification steps, and what content or order data must not be changed until the restore decision is complete.
Use the checklist to separate a bad plugin update from a host outage, malware cleanup, accidental deletion, failed migration, or WooCommerce data-loss event. Each disaster recovery scenario has a different restore point, approval path, and acceptable downtime.
After restore, verify the homepage, login, media, forms, checkout if active, search-critical pages, sitemap, robots directives, and recent business records. A restore is not complete until the site owner can confirm the recovered state matches the intended recovery point.
Review this disaster recovery checklist whenever hosting, payment flows, membership features, backup storage, or agency ownership changes. Recovery plans become stale when the site architecture changes faster than the documentation.
Download
Last updated 2026-09-14.