A restore can help after an accidental deletion or a problematic update. It can also replace valid data with an older version. Before starting, decide what needs to return, what must be preserved and which recovery point is suitable. Available tools, backup copies and assistance depend on your service.
1. Describe the problem and the intended result
Record the domain, affected application, missing or broken items, and the last known working date and time, including the time zone. Note recent changes. Recovering a deleted file, reversing an update and restoring an entire account require different interventions.
If you suspect an intrusion, report it before restoring. An older copy may already contain the problem; rolling back does not by itself resolve the cause of a compromise.
2. Confirm the available copies and method
Use your Client Area to ask our team to confirm the accessible tools, available restore points and scope of the operation. Mention whether you have your own archive. Do not include a password or a complete archive in the message; ask for an appropriate transfer method if needed.
The native cPanel backup tool distinguishes partial copies from a complete account archive. Automatically restoring a full archive requires the hosting provider or an administrator; it is not a customer cPanel account feature.
If your service offers JetBackup, the items you can restore depend on the available copies and permissions. Check the actual selection: a “full account” label alone does not establish that everything will be included. Do not change a merge or replacement option without understanding its effect.
3. Protect recent changes
Compare the backup date with orders, form submissions, uploaded files and other changes made since then. Confirm which ones could be replaced and how to preserve them. If the scope includes email or account settings, consider their impact too. Prepare a copy of the current state where possible and appropriate, following our backup preparation guide.
For a site that receives new data, agree on a maintenance window and a way to limit new changes with your developer or our team. A production restore should not be used as a trial run. Where possible, validate the copy in a separate environment first.
4. Choose a consistent set of data
Restore only what is necessary while accounting for dependencies. For WordPress and similar applications, files and the database need to be consistent. Mixing versions without checking them can leave incompatible content or features. Also confirm database access if it needs to be restored.
Have the space required for the chosen method checked. There is no universal quota multiplier that applies to every restore. Before confirming, review the domain, date, time zone and selected items. If the summary differs from the agreed scope, stop and ask for clarification.
5. Follow progress and test the result
Follow the status provided by the tool or our team. In JetBackup, a pending or processing task is not a completed restore. If it fails or the outcome is uncertain, keep the message and task reference; ask for a check before starting the operation again.
- Open important pages and check the expected images, documents and content.
- Test sign-in and essential features using appropriate test data, without triggering real payments or customer notifications.
- Check that recent data to be preserved and the account items included in the intervention are present.
- Report any remaining errors with their time and exact wording.
A completed status does not replace these checks. If an update or incident prompted the restore, plan to address its cause before repeating the same changes. Then confirm that backups have resumed using our automatic backup guide.
References: cPanel Backup Wizard, JetBackup restoration, JetBackup task status and WordPress backups.
