What should a website backup contain?
A backup is a retained copy intended to help recover information after loss or an unwanted change. For a website, the required material depends on its technology. Files alone may not include database content, orders or settings. A useful backup arrangement includes a clear, tested way to restore what the business needs.
Useful context
- Identify the website platform and any database or order information it uses.
- Ask who runs backups, where they are retained and who can restore them.
How it works
Check the coverage
For WordPress, both files and the database matter. Other platforms have different export and recovery limits. Ask whether uploads, settings and recent submissions are included. A screenshot or a list of page URLs is a reference, not a working recovery copy.
Check the age of the restore point
A backup from yesterday may not contain today’s enquiries or orders. Decide how much recent information the business could afford to lose and compare that with the actual schedule. More frequent copies are useful only if their coverage and recovery route are reliable.
Keep copies protected
Backups can contain personal information and sensitive configuration. They should not be downloadable from a public website folder or shared indiscriminately. Confirm access controls and retention so protection against data loss does not create a different exposure.
Prove restoration safely
Ask for a recovery check in an isolated environment with live email and payment actions disabled. Record what was restored and what was not. Do not test by overwriting the production website, particularly when fresh customer activity could be lost.
What to check
- The backup includes the components the website actually needs.
- You know the latest usable recovery point.
- A named person can perform a safe restore.
Sources and further reading
Platform features can change. Check the provider’s current guidance before changing a live service.