cPanel Backup Restore

Log in to cPanel, open Files → Backup → Restore, and select the component matching your partial backup. Current cPanel documentation uses Select Restore Type; older layouts may show separate restore boxes. One upload restores the chosen component, not the whole account.

Save the current files and database before overwriting them, choose a trusted recovery point and check whether newer messages or orders must be preserved. A successful upload is not proof the application and its data are consistent.

1. Open cPanel → Files → Backup and click Restore. Backup Wizard offers a guided route.
2. Under Select Restore Type, choose Home Directory, the database, email forwarders or global filters to match the file.
3. Click Choose File, select the backup from your computer, then click Upload.
4. Wait for the progress page to finish without errors, then load the site or check the forwarder list to confirm.

• Overwrite warning: files at matching paths can be replaced by older archive copies; separately created files may remain, so inspect the result rather than treating this as a clean rollback.
• Filters scope: the filter backup holds only global email filters, not filters set inside a single mailbox.
• Disk quota: upload and extraction need available space. For a full-account WHM restore, cPanel's documentation requires at least twice the archive size free on the server.
• Never upload a full-account tar.gz here: its layout (homedir/, mysql/, etc/) unpacks as extra folders inside your home directory.

When you hold a full-account tar.gz but only a cPanel login, extract it on your computer and restore the pieces manually: website files through File Manager, database through phpMyAdmin. This avoids waiting for a WHM restore when only the site needs to come back.

1. Extract the archive locally (7-Zip on Windows, or tar -xzf on macOS and Linux).
2. Inside, open homedir/public_html — that folder is the website. Zip it, upload through cPanel File Manager and extract over the damaged copy.
3. Inside mysql/, find username_dbname.sql. In phpMyAdmin, select the empty or damaged database and use Import.
4. Check the site’s config file (for WordPress, wp-config.php) still matches the database name, user and password on the server.

phpMyAdmin rejects files above the server’s upload limit; the large SQL import guide covers splitting the dump or using the command line. Where Terminal is enabled in cPanel, a compressed dump imports directly:

gunzip < username_dbname.sql.gz | mysql -u username_dbuser -p username_dbname

cPanel itself does not schedule backups from the Backup screen — the hosting provider’s backup system does, and on WebJi® those copies appear in JetBackup. The Backup icon in cPanel lets you download and restore manually; it does not mean an offsite copy exists.

For a copy held outside the hosting server, WebJi® server backup solutions start with the Backup.Help app and 200 GB storage at ₹1,300 a month before 18% GST. The 3-2-1 backup rule explains why one on-server copy is not enough for a business site.