Practical hosting guide
Restore Website Files, Databases and Email
Select a recovery point and restore the right data without overlooking recent orders or messages.
Identify the incident before restoring
Record when the problem started, which data is affected and whether the site is still accepting orders or enquiries. Preserve a copy of the current state where possible before replacing anything.
For suspected compromise, isolate the affected service and investigate the entry point. Restoring a backup without fixing vulnerable code or access can allow the incident to recur.
Select a clean, compatible recovery point
Check that the required website files, database and email are actually covered by your backup service. Choose a point before the incident and compare its age with your acceptable data loss.
File and database versions need to work together. If an ecommerce database is restored, reconcile orders and payments created after the recovery point with the appropriate business systems.
Restore and verify
- Use a staging or isolated environment to validate the backup where practical.
- Download an independent copy and confirm the restore scope shown by the control panel.
- Restore only the files, database or mail data required for the incident.
- Test navigation, login, forms, HTTPS, order flow, scheduled jobs and external integrations.
- Monitor logs and resource use, and secure accounts or code affected by the incident.
Check the available backup tools
Use the tools enabled on your actual hosting package and confirm whether email is included. The platform’s manual Backup/Restore documentation describes local package exports and restores.
Self-managed VPS needs its own backup and restore process. See backup options and retention or ask support about your plan before relying on a recovery service.
