A full account backup and an application-specific backup can contain different data. A website may need both its files and its database to be restored consistently, while email, account settings or other websites may fall outside a narrower application backup. Before a major change, identify exactly what you need to preserve and confirm that the backup has completed successfully. A request to start a backup is not evidence that a usable archive already exists.

For supported cPanel accounts, a manually generated full backup can be stored in the account's home folder for download. It may use account storage, so keep sufficient free space and move an appropriate copy to a secure independent location. Avoid leaving backup archives publicly accessible through a website. Full account restoration may require our assistance even when you can generate the archive yourself.

1. Open cPanel for the intended service, find Backup, then select Download a Full Account Backup.
2. Choose Home Directory as the destination when you have enough account space. Enter a monitored address for the completion notification.
3. Review the integration-links option if shown. Including those links can include external account credentials, so include them only when the recovery plan requires them.
4. Select Generate Backup once and wait for completion. Download the finished archive from the available-backups list over your authenticated connection.
5. Store a verified copy securely outside the hosting account. Full-account restoration requires the supported provider or WHM workflow; this cPanel screen does not automatically restore the full archive.

1. Review the backup date and the data that will be replaced. Newer orders, uploads, edits or messages may be lost if their data is overwritten by an older copy.
2. Preserve current information that must survive and choose the narrowest appropriate restore scope.
3. After restoration, verify the website, its database-dependent functions and any affected email.

Backup availability is a recovery aid, not a guarantee that every past state or deleted item can always be recovered.

The strongest check is a supported restore into an isolated test destination, followed by opening representative files and testing the restored application and database together. Arrange this with us if the account cannot restore independently. Confirm that the test copy cannot send live customer notifications or process real transactions. Checking the archive contents and restore procedure is useful preparation, but it does not replace a successful recovery test.

1. Identify whether the available copy covers the full hosting account, one website, its database or selected files.
2. Wait for a requested backup to complete and record its timestamp and location.
3. Confirm how the intended data can be restored, including any full-account restore that needs our assistance.

Download an appropriate independent copy when your recovery plan requires it, and store it securely outside public web folders. An enabled schedule is not proof that the latest run succeeded. Check retention and completion before deleting the only other copy of important data.

• Uploading and managing website files in the Account Manager
• Managing databases, users and application connections
• Protecting your Web Hosting website and responding to a compromise
• Building a Web Hosting website with SitePad

• Nabtech Web Hosting
• cPanel: full backups and restoration limits