Backup Wizard: create backups you can actually recover

A useful backup includes the data needed to restore a working service, not merely a copy of its homepage. For database-driven websites, coordinate the file and database versions.

Make a recovery-ready copy

1. Open Backup Wizard and choose the appropriate backup scope.
2. For a full account copy, check available storage and the destination. Avoid leaving archives inside a public document root.
3. Wait for generation to complete before downloading. A started job is not proof of a valid backup.
4. Store the archive privately away from the hosting account and label its date, scope and application release.
5. Test a restoration into a safe separate environment periodically.

Know what you can restore

cPanel account users can restore supported partial backups through the available interfaces. Automatic full-account restoration generally requires the provider’s WHM access. Confirm support arrangements before relying on a full archive as your only recovery plan.

Quota exhaustion can stop backup generation. Keep enough working space and verify archive integrity. An archive containing client information or credentials needs the same care as the live system.

Before an upgrade, record the exact files and database that belong together. Avoid restoring an old database over recent orders without understanding the data loss and agreeing a recovery point.