Restoring a website can overwrite changes made after the selected backup was created. Before requesting a restore, identify what failed, when it last worked and which components need recovery. A targeted file or database restore may be more appropriate than replacing an entire account, depending on the problem and available backup format.
Recommended workflow
- Choose the latest suitable recovery point from before the problem and explain why that point was selected.
- Agree whether the restore affects files, databases, mail or the whole account, and plan any necessary maintenance window.
- Check the restored application and compare recent data with the preserved current copy before closing the request.
Record any new orders, customer records, uploads or messages that could be affected. Preserve a separate copy of the current state before applying the older backup, even if that state is partly broken. This provides a reference for extracting newer data or reversing a restore that does not resolve the issue.
Provide the service reference, requested restore point and intended scope in your support ticket. Confirm the backup is available and compatible before approving a production change. Assistance depends on the purchased plan and supported source; additional work can require a separate quote. After recovery, test the affected function and check dependent services such as email, scheduled jobs and external integrations.
