Skip to content

Backups

Create, inspect, and restore protected account backups.

1Overview

Backups coordinates account archives that can include website files, databases, application source, mail, and panel metadata. Restore is a privileged operation with integrity checks.

Backups in the administrator panel. Account names, domains, and addresses are examples. Available controls depend on your package and server configuration.
Administrator Backup and Restore page with account selection, backup creation controls, and backup history.

Backups in the administrator panel. Account names, domains, and addresses are examples. Available controls depend on your package and server configuration.

2Before you begin

Administrator actions can affect multiple customer accounts and server services.

3Step-by-step workflow

Open Backups, select the account and backup scope, create the archive, wait for its completed status, and download or retain it according to policy. For restore, choose the exact backup and read the proposed changes first.

  1. Open Backups and choose the hosting account, backup scope, and destination.
  2. Check available storage and decide whether the archive needs files, databases, mail, or the supported complete account scope.
  3. Start the backup once and watch its queued or running state.
  4. Use Cancel on the intended queued or running job if it was started by mistake; wait for the final cancellation state.
  5. Rely on an archive only after the job shows Completed and the expected download is available.
  6. Retain a copy outside the hosting account according to your recovery plan.
  7. Before restoring, take a fresh backup and confirm which files and databases will be replaced.
  8. After a restore, test the website, database connection, mail, and account access before ending maintenance.

4Practical example

Example: a panel update backup protects panel code or metadata according to its displayed scope. It is not automatically a full backup of every customer website, SQL database, or email message.

5Verify the result

Validate the outcome from the affected account or an independent client connection, not only from the administrator screen.

  1. Confirm the archive is listed with a successful completion state.
  2. After a restore, test the affected website, database, and mail data before closing maintenance.

6Common problems and what to check

A job remains queued: review the backup worker and earlier running jobs before creating another request.

A backup fails: check free storage, ownership, and the job error; do not use an incomplete archive.

Restore changed newer content: use the pre-restore backup and the approved restore scope to recover the required version.

7Security, impact, and rollback

A restore can overwrite newer files and database data. Take a fresh backup before restore, verify free storage, and schedule downtime for production websites when required.

Related guides

SFTPProvide secure file-transfer access and inspect account transfer settings.Cron JobsReview and manage scheduled work.See all guides in Administrator panel

Still need a hand?

Get help with your plan, website, or hosting through your client area.

Open client area