When your website's full backup archive is too large, the control panel's built-in restore tool may time out, get stuck partway through, or simply refuse the upload. This usually happens with sites that have a lot of images, videos, or other media, or a database that has grown large over time. The fix is to get the archive onto your server a different way and unpack it there, instead of relying on the browser-based upload form.
Why Large Backups Fail to Restore
A few things commonly cause this:
- Your hosting account has a maximum file upload size, and the backup archive is bigger than that limit.
- The browser upload times out before a very large file finishes transferring, especially on a slower connection.
- The restore process itself runs out of time trying to extract and import a very large archive in one step.
How to Restore a Large Backup
Instead of uploading the whole archive through the restore tool in one go, upload it directly to your account using FTP or SFTP, then extract and restore it from there. This avoids the browser upload limit entirely, since FTP clients don't impose the same file size restrictions.
In cPanel
- Connect to your hosting account using an FTP or SFTP client, with the same login details you use for cPanel.
- Upload the backup archive (usually a .tar.gz or .zip file) into your home directory, outside public_html.
- Log in to cPanel and open File Manager.
- Locate the uploaded archive, select it, and click Extract to unpack it directly on the server, no browser upload required for the extraction step.
- Move the extracted website files into public_html (or the correct folder for an addon domain) using File Manager's Move option.
- Find the .sql file inside the extracted backup and import it through phpMyAdmin if it's small enough to accept.
In DirectAdmin
- Connect to your hosting account using an FTP or SFTP client.
- Upload the backup archive into your account's home directory.
- Log in to DirectAdmin and open File Manager.
- Locate the archive and use the Extract option to unpack it on the server.
- Move the extracted files into your domain's public_html folder.
- Import the database from the extracted .sql file through phpMyAdmin if it's within its upload limit.
Restoring a backup overwrites your current files and database, and this can't be undone. Take a fresh backup of your live site before you restore an old one, so you have a way back if something goes wrong.
If the Database Itself Is Too Big
Sometimes it's not the full archive that's the problem, it's the database dump inside it being too large for phpMyAdmin to import on its own. If that's the case, see How to Import a Large MySQL Database When It's Too Big for phpMyAdmin for a method that gets around that limit.
If your account doesn't have FTP or SSH access set up, or the backup is too large to handle through any of these methods, reach out to support with the backup file's size and where it's currently stored, so it can be restored for you directly on the server.