Restoring an account from a WHM backup

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.

1. Choose the correct restoration workflow. Use Backup Restoration for supported scheduled backups; a cpmove archive uses Transfer or Restore a cPanel Account.
2. 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.
3. 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.
4. In Backup Restoration, select the account and available backup date through the appropriate account/date tab. Review all options, including account and IP handling.
5. 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.
6. 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.
7. 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.

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 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.

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.

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.

• Configuring WHM backups and retention for the available storage
• Selecting files for a WHM file restoration
• Planning DNS and mail cutover after a WHM transfer
• Investigating a failed WHM backup job

• cPanel: Backup Restoration
• cPanel: Transfer Or Restore A cPanel Account