Test website restoration before an incident

Define what must be recoverable

Inventory code, content, databases, uploads, media, application settings and scheduled jobs. Some elements live with the host, others in a CMS, separate storage or a third-party service. Distinguish what can be rebuilt from what would be lost permanently.

Set an acceptable recovery point for each set: a brochure site updated monthly and a service receiving daily enquiries have different needs. Record copy frequency, location, retention and who can initiate a restoration.

• Inventory of necessary content and data.
• Acceptable recovery point for each set.
• Copy locations and accountable people.

Separate copies, exports and restoration

An editorial export may retrieve text but omit themes, settings, users or media. Files alone may omit the database. Ask the provider exactly what its service covers and what remains your responsibility. WordPress documentation recommends backing up before plugin updates; the exact method depends on the architecture.

Protect copies according to the context and limit who can read or replace them. Document restoration prerequisites without publishing credentials, keys or access details in a shared guide.

Rehearse in an isolated environment

Choose a copy and restore it away from the public website. Time the steps instead of assuming the written procedure is complete. Check pages, media, links, required permissions, the form in test mode and functions that rely on external services.

Compare restored data with the initial inventory. Record absent items, the latest change present and settings that need rebuilding. A successful exercise should be repeatable by another authorised person within the time the organisation considers acceptable.

• Copy and environment used.
• Observed duration and manual steps.
• Pages, data and functions actually checked.

Fix the plan and schedule the next exercise

Update the procedure after each rehearsal: contacts, operation order, dependencies and exit checks. Repeat after a migration, provider change or significant application update. The maintenance guide puts restoration checks into regular site operations.

During a real incident, preserve useful diagnostic information and coordinate recovery with the responsible people. A restoration test reduces uncertainty; it does not guarantee zero loss or a third party’s availability.