FIELD NOTE · Hosting Fieldbook
A backup plan needs a restore test
Check whether the copy can bring the website back, not just whether a download exists.
List everything required to recover
For a static website, the essential materials may be page files, assets, configuration, and domain/DNS records. A database-driven site also needs a matching database export and application configuration. An uploaded media folder alone is not a full WordPress recovery set. WordPress’s backup documentation distinguishes files from the database; use its current instructions for the installation you manage. Store passwords through an appropriate password manager rather than adding them to a public archive.
Keep a dated copy away from the live account
A copy stored only beside the live site can disappear in the same account failure. Choose an independent location that the owner can access. Record the site, backup time, application version where relevant, what is included, and who can restore it. A sample schedule might combine a regular backup with another copy immediately before a planned change. The interval should follow how much work the business could reasonably lose, not a universal schedule copied from another site.
Restore into an isolated test destination
Use a destination that cannot send real customer messages, take payments, or overwrite production. Confirm which automated jobs and integrations must be disabled before starting the test. Ask the responsible technical person to open representative pages, inspect images, and verify a safe sample of application behavior. Keep search indexing off the recovery destination. Testing a real recovery is different from simply checking that an archive opens.
Record the result as an operating procedure
Write down elapsed recovery time, missing pieces, required access, and the person who completed the test. For example, a restore might succeed but depend on an undocumented database password; that is an access problem to fix before an emergency. Retest after a substantial platform or ownership change. A backup is one part of recovery, alongside domain access, supplier contacts, and a clear decision about which version is safe to restore.
Check the original guidance
Sources checked October 31, 2026. Supplier requirements and platform rules can change.
Prepared with AI assistance. Examples are constructed for explanation, not reported customer results. Corrections are welcome through the contact page.
← All guides