A WordPress backup is useful when it can restore the website and the business information you need. Check both files and the database, then test recovery away from the live site. Spout’s WordPress care starts from K450 a month, confirmed in your written quote; agree the backup coverage and recovery responsibilities explicitly for your website.
What does your backup need to contain?
WordPress separates its files from the database. Its backup handbook explains why a recovery plan needs both. Files include uploaded images, themes and plugins; the database holds content and settings. Source checked 19 October 2026.
For the business owner, turn that distinction into a list of things you expect to recover. Include pages, photographs, customer orders and the configuration that makes enquiries or checkout work. Ask the person maintaining the site to identify which backup contains each item.
Keep related services on a separate list. Your domain account, mailbox history and payment-service records may sit outside the WordPress installation. Do not assume a website backup includes them. A recovery plan should state how those dependencies are accessed and who controls them.
How often should you save a copy?
Choose the frequency from the amount of work the business could afford to reconstruct. A brochure site updated occasionally and a shop receiving orders throughout the day have different needs. A generic daily schedule is not automatically right for both.
Ask a plain question: if the latest recoverable copy were restored now, which new orders, enquiries or edits would be missing? Then decide how much of that loss is acceptable and what backup arrangement would address it. That decision belongs to the owner, with the technical consequences explained.
Save an additional recovery point before significant changes. Keep enough history to recover from a problem noticed later, rather than replacing every useful older copy immediately. The exact frequency, retention period and storage limits should be written into the agreement, not inferred from a plugin’s marketing page.
How can you test recovery safely?
Our suggested recovery exercise uses a separate, private test environment. Agree its scope with the account owner first. A restored shop can contain real customer information, so access and data handling need care even when the public cannot see it.
| Check | Evidence to keep | Question it answers |
|---|---|---|
| Restore the chosen backup | The backup identifier and restore result | Can this copy actually be used? |
| Open important pages | A short list of pages checked | Are the content and images present? |
| Compare business records | An authorised check of recent records | What would be missing at this recovery point? |
| Check forms safely | A controlled test with external effects disabled or agreed | Does the enquiry journey still function? |
| Check integrations safely | Documented test settings and outcomes | Will a restored copy accidentally contact customers or take money? |
This table is an original acceptance checklist, not a report of a client restoration. Do not send real customer messages or run real payments from a test copy merely to prove that it boots.
What should happen after a failed test?
Keep the working production site untouched while you investigate the copy. Identify whether the problem is a missing file, an incomplete database export, unavailable access or a dependency that the restored site cannot reach. Record the fault and the person responsible for resolving it.
Repeat the test after the correction. A successful download is different from a successful restore, and a successful restore is different from a functioning customer journey. Keep those results separate so the owner knows what has actually been proved.
WordPress’s security handbook recommends checking that backups are valid and recoverable. Source checked 19 October 2026. The practical business decision is what evidence you require from your provider, and what happens when that evidence is missing.
Who should be able to recover the website?
Nominate an accountable person and a cover arrangement. The plan needs a route to the backup, the hosting account and the relevant recovery contacts if the usual developer is unavailable. Store access securely; do not scatter shared passwords through staff chat groups.
Consider the business’s account ownership as well as technical access. If every recovery option depends on a former employee’s personal address, the plan has a weakness that another backup file will not solve. Review account owners when staff or service providers change.
Also agree who can authorise a live restoration. It may replace orders or edits made after the chosen backup. Before using it, compare the proposed recovery point with current business records and decide how missing work will be reconciled. A restore should be a considered business action.
Is recovery included in your care price?
Ask that directly. Spout’s WordPress care starts from K450 a month, confirmed in your written quote. The written scope should identify backup arrangements, test coverage and how a recovery request is handled. It should distinguish routine care from work on an already damaged or unsupported installation.
For a wider support arrangement, see Mission Control. Check hosting separately if the current host controls the only backup copy. No starting price in this guide should be read as a guaranteed recovery time or a promise that every incident is included.
Bring your website address, current backup arrangement and the business records you could least afford to lose when you request a WordPress care review. A useful plan leaves you knowing what can be recovered, who can do it and what evidence supports that confidence.
Spout Team. Prepared with AI assistance; sources checked on 19 October 2026.