A useful website backup includes the information needed to recover the site, not just its visible pages. Depending on the platform, this can include files, databases, uploaded media, and configuration.
Before an update or migration
- Identify the site, its hosting account, database, and any other systems it depends on.
- Confirm what your existing backup service covers, how often it runs, and how far back copies are retained. Do not assume a backup service is included without checking your plan.
- Create an additional backup before a significant change where your available tools support it.
- Store a protected copy separately from the live site and confirm that the backup completed successfully.
Using cPanel tools
If enabled for your account, cPanel’s Backup or Backup Wizard can create full or partial backups. Choose the scope that matches what you need to recover. A database-backed site generally needs its database as well as its files.
Restoration options differ by backup type and account permissions. Full-account restoration may require your hosting administrator; it is not the same operation as uploading a single file or restoring one database.
Before you request a restore
Specify the desired recovery point and why you need it. A restore can replace changes made after that point, including new orders, form submissions, uploaded files, or website edits. Decide whether the entire site or one component should be restored.
Preserve a copy of the current state where possible. For a live business site, agree the timing and post-restore checks before work begins.
What to include in your ticket
- The domain and affected platform or component.
- The time the problem began and the last known working time.
- The backup location and date, if known.
- Changes made since the backup and any business data that must be preserved.
Availability of a particular recovery point must be confirmed; a restore request is not a guarantee that a suitable backup exists.
Further guidance: cPanel: Backup Wizard.
