A backup notification tells you that a job ran; it does not prove the website can be recovered. Before accepting a maintenance arrangement, ask the agency to demonstrate a safe restore and explain which parts of the business are outside that backup.
Related service: Website and ecommerce development- 01List the components to protect
- 02Select a consistent backup set
- 03Restore into an isolated environment
- 04Verify content and safe workflows
- 05Record gaps and rehearse again
SECTION 01
Define the backup boundary with the agency
Ask what is included: source code, uploaded images, content database, redirects, configuration and any form records held by the website. Some information may live in a separate provider with its own recovery process. Identify those dependencies explicitly. Agree how much recent change the business could tolerate losing and how quickly it needs key functions restored, then assess whether the proposed arrangement can support those needs.
WordPress's backup documentation illustrates why files and database content can require separate protection. Vercel's rollback documentation illustrates another boundary: reverting a deployment does not automatically reverse every external service or data change. These are examples for reviewing your actual stack, not instructions to add either platform. Ask the agency to name the protected components and the evidence for each.
SECTION 02
Illustrative example: recovering a deleted resource library
Imagine a training company accidentally deleting several downloadable guides and their page records. A code rollback restores the old page template but not the missing uploads or content database entries. A useful rehearsal restores a consistent backup set in a protected test environment and checks that each recovered page opens the intended document. The team also verifies that newer content is not silently lost during the proposed recovery.
The first exercise uses synthetic form submissions and disables real outbound notifications. Staff record the backup's date, the recovered content and the gaps they found. They then decide whether to restore selected records or use a broader recovery procedure. This example shows why a controlled rehearsal is more informative than intentionally breaking the live website to see what happens.
SECTION 03
Accept a recovery report rather than a green dashboard
The report should identify the backup selected, restoration steps, observed recovery time, tested pages and any unavailable dependencies. Verify downloads, images, access permissions and a safe lead-submission path. Check that restored settings do not reconnect test actions to production email, payments or other external effects. An observed rehearsal time is evidence for that exercise, not a universal recovery guarantee.
More frequent backups cost storage and operational attention, while infrequent backups risk losing recent work. Choose the arrangement from business needs rather than an arbitrary package label. Handoff should name the recovery operator, secure access method, escalation route and next rehearsal trigger. Retest after significant changes to hosting, content storage or integrations, because yesterday's successful procedure may no longer cover today's website.
SECTION 04
Frequently asked questions
Is a deployment rollback the same as restoring a backup?
No. A rollback can restore application code while databases, uploads or external provider state remain unchanged.
Should we test recovery on the live site?
Prefer an isolated environment with real outbound actions disabled. Avoid destructive production experiments merely to demonstrate a backup works.
What evidence should a maintenance agency provide?
A scoped recovery report showing the backup used, restored components, executed checks, observed timing and any unresolved gaps.
PRIMARY REFERENCES
Sources and further reading
These references cover the standards, platforms, or published prices discussed in the guide. Worked examples and checklists are our editorial guidance.
EDITORIAL METHOD
About this guide
We use AI to assist with drafting and editing. Catapult AI Work is responsible for the published content. Examples illustrate possible approaches; they are not client case studies unless identified as such.
Budget examples are not Catapult package prices. Check linked provider pages for current fees and plan limits before making a purchase.
Read the editorial policy