Restoring a full cPanel account backup allows you to recover all data, databases, emails, and settings from a backup file or cpmove archive. The restore process recreates the entire account exactly as it existed when the backup was created, making it essential for disaster recovery, server migrations, or account transfers.
This guide explains how to restore cPanel backups using the correct file formats and locations, with important warnings to ensure a successful restoration process.
Important Version Update
Warning: The legacy restore interface was removed in cPanel and WHM version 90. If you are running version 90 or later, you must use WHM's Transfer or Restore a cPanel Account interface instead. You can find this tool by navigating to WHM >> Home >> Transfers >> Transfer or Restore a cPanel Account.
This modern interface provides enhanced functionality and improved reliability for account restoration and transfer operations. Contact support@obhost.org if you need assistance determining which version you are running.
Critical Warnings Before Restoring
Before you begin any restore operation, understand these critical requirements:
Do not interrupt server processes: The restore system uses multiple applications including MySQL databases. Never shut down or restart any processes on the server during the restore operation, as this will corrupt the restoration and potentially damage your data.
MySQL configuration requirement: Do not use the skip-name-resolve setting in your MySQL configuration. This setting causes serious issues with server operations, including account transfers, backup restorations, and phpMyAdmin access. Unless you are an advanced MySQL administrator, avoid this setting entirely.
Supported Backup File Formats
The restore feature recognizes specific filename formats only. Your backup file must use one of these naming conventions:
- cpmove-{USER}
- cpmove-{USER}.tar
- cpmove-{USER}.tar.gz
- {USER}.tar
- {USER}.tar.gz
- backup-{MM.DD.YYYY}{HH-MM-SS}{USER}.tar
- backup-{MM.DD.YYYY}{HH-MM-SS}{USER}.tar.gz
- backup-{MM.DD.YYYY}_{HH-MM-SS}_{USER}.tar
- backup-{MM.DD.YYYY}_{HH-MM-SS}_{USER}.tar.gz
Replace {USER} with the actual cPanel username. For date-stamped backups, use the format MM.DD.YYYY for dates and HH-MM-SS for times.
Required File Locations
For the restore feature to locate your backup file, it must reside in one of these specific directories on your server:
- /home
- /usr/home
- /web
- /home2
- /home3
- /root
- /usr
Alternatively, you can upload a backup file from your local computer using the file selection option in the restore interface. This is useful when transferring accounts between servers or restoring from local backups.
Understanding the Restore Process
When you initiate a restoration, the system automatically expands the compressed backup archive in its current directory. This expansion requires sufficient free disk space, typically at least twice the size of the compressed backup file.
The restore operation recreates the following account components:
- All website files and directory structures
- MySQL and PostgreSQL databases with user permissions
- Email accounts, forwarders, and filters
- DNS zone configurations
- SSL certificates and security settings
- Cron jobs and scheduled tasks
- FTP accounts and permissions
During restoration, the system validates data integrity and maintains proper file ownership and permissions. The process duration depends on backup size and server resources, ranging from minutes for small accounts to hours for large, database-heavy websites.
Best Practices for Successful Restoration
Follow these recommendations to ensure smooth backup restoration:
Verify disk space: Confirm you have sufficient free space before starting. Check both the backup location and the destination account directory.
Check file permissions: Ensure the backup file has proper read permissions for the restore process to access it.
Avoid peak hours: Schedule restorations during low-traffic periods to minimize server load and reduce potential conflicts with active services.
Test after restoration: Always verify website functionality, database connections, and email delivery after completing the restore process.
Document the process: Keep records of what was restored, when, and from which backup file for future reference and troubleshooting.
Troubleshooting Common Restore Issues
If your restoration fails or encounters errors, check these common causes:
Filename format mismatch: Verify your backup file uses one of the supported naming conventions exactly as specified.
Incorrect file location: Confirm the backup file exists in one of the approved directories listed above.
Corrupted backup: Test the integrity of compressed archives before attempting restoration. Corrupted files will fail during extraction.
Insufficient permissions: The restore process requires appropriate system permissions. Root access may be necessary for certain operations.
Conflicting accounts: If an account with the same username already exists, you must either remove it first or restore to a different username.
What happens to existing data when I restore a backup?
The restore process completely replaces the existing account with the backup version. All current files, databases, emails, and settings will be overwritten with the backed-up versions. Always create a current backup before restoring older data if you need to preserve any recent changes.
Can I restore only specific parts of a backup instead of the whole account?
The full account restore feature restores the entire account as a unit. For selective restoration of individual files, databases, or emails, use the specific backup restoration tools available in cPanel's backup interface or contact OBHost support for assistance with partial restorations.
How long does a typical backup restoration take?
Restoration time varies significantly based on account size and server resources. Small accounts under 1 GB may restore in 5-10 minutes, while large accounts with extensive databases can take several hours. Monitor the restoration progress through the WHM interface or log files.
What should I do if the restoration process appears stuck?
First, verify that no server processes were interrupted and that MySQL services are running normally. Check available disk space and system logs for error messages. If the process remains stalled after 30 minutes beyond the expected completion time, contact support for assistance before attempting to restart or cancel the operation.
The OBHost support team is available 24/7 to assist with backup restorations and troubleshooting. For technical assistance with the restore process, contact our support team at https://www.obhost.net/contact or email support@obhost.org.
