A full-account restore can replace website files, databases, mail and account configuration with an earlier state. Prepare a recovery plan that preserves valuable changes made after the backup, especially orders, customer submissions and messages.
IN THIS ARTICLE
Prepare for the change
Confirm the account owner’s authorised recovery point and scope. Verify the backup’s identity, completion and availability, plus destination capacity and software compatibility. Make a current preservation copy before overwriting live data, even when the current site is broken.
01 Restore an account from a WHM backup
- Choose the correct restoration workflow. Use Backup Restoration for supported scheduled backups; a
cpmovearchive uses Transfer or Restore a cPanel Account. - Prefer an isolated test restore when time permits. Check that the archive contains the expected files, databases and mail rather than only a partial backup.
- For a live recovery, pause writes or place the application in its supported maintenance mode. Record the final live data cutoff and preserve anything that must be reconciled later.
- In Backup Restoration, select the account and available backup date through the appropriate account/date tab. Review all options, including account and IP handling.
- Add the precise recovery item to the restoration queue and run it. Monitor completion and read warnings or failed components instead of treating queue acceptance as success.
- Verify application reads and writes, administrator access, mail, DNS, certificates, scheduled tasks and file ownership. Compare critical record counts and recent business data against the selected recovery point.
- Reconcile preserved newer data through an application-aware procedure, then reopen writes and monitor. Retain the pre-restore preservation copy until the recovery is accepted.
Check the backup or recovered data
The account should operate from the intended recovery point with a clear record of any newer data deliberately reconciled or excluded. Confirm external DNS still points to the correct service and no test environment sends duplicate notifications.
If the change does not work
If only some components restore, stop and inspect the per-component log before retrying. Repeated full restores can overwrite successful corrective work. If the backup predates a security incident, still close the original entry point and rotate affected credentials before public use.
Will a restore merge today’s orders with last week’s database?
Do not assume that. A database restore normally returns stored data to the selected state. Merging business records requires application knowledge, a preserved current copy and careful handling of identifiers, payments and related records.
When should I restore only files?
If the problem is one deleted asset or a known damaged code file, a targeted file restore may preserve current database and mail activity. Confirm that the selected file version remains compatible with the live application before choosing the narrower recovery.