Last modified: June 26, 2020
If you enable system backups, your server saves system backup files in the local backup directory (
/var/cpanel/backup) by default. You can also save system backup files to an additional destination. You can do this manually, via API, or via WHM’s Backup Configuration interface (WHM >> Home >> Backup >> Backup Configuration).
/usr/local/cpanel/bin/backup script uploads a
.tar file that contains all of the system backup files to each destination that you configure to receive system backups. The system only sends system backup files to destinations whose files contain a
upload_system_backup value of
- cPanel & WHM does not include an interface to restore system backup files. To restore content from system backup files, you must perform the restoration manually.
- The additional destination configuration file uses YAML format, which contains a simple associative array.
- For security purposes, ensure that the destination server is on your secure network. If your backups will not transfer to a server on your secure network, use a secure method such as SFTP, Amazon S3™, or WebDAV with SSL.
How to enable system backup file saves
To enable system backup file saves, you can perform one of the following actions:
Select the Back up System Files checkbox in the Backup Settings tab in WHM’s Backup Configuration interface (WHM >> Home >> Backup >> Backup Configuration).
Use the WHM API 1
backup_config_setfunction and set the
System backup files and directories
The server backs up DNSSEC databases as part of the system files backup. The system can corrupt the DNSSEC database if it encounters an Out Of Memory (OOM) or disk full condition. The system administrator can also corrupt this database inadvertently.
The system administrator can restore the database from the system backup files. If they do not back up system files, they will need to perform the following steps:
- Rebuild the
PDNS.dbfile from scratch.
- Regenerate the DNSSEC keys for each domain that lost its DNSSEC key.
- Tell users to register the new DNSSEC keys with their domain registrar.
cPanel & WHM backs up the following files and directories:
To configure system backups to include custom files or directories, create a new file or directory in the
/var/cpanel/backups/extras directory (for example,
/var/cpanel/backups/extras/etc). In that file, enter an absolute path to any files that you wish to back up (for example,
The server administrator can edit the
/etc/my.cnf file to change the MySQL® data directory location. The system will back up the directory at its new location.
How to configure an additional destination to receive system backups
To configure an additional destination to receive system backups, perform one of the following procedures:
In WHM’s Backup Configuration interface, select the Additional Destinations tab and enter the additional destination’s information.
Make certain that you select the Transfer System Backups to this Destination checkbox.
Manual configuration method
To manually modify the configuration file of an additional destination, perform the following steps:
- Identify the configuration file in the
- Each destination requires its own configuration file.
- The file name contains the destination name, the User ID (UID) label, and a UID character string. For example:
The UID sequence prevents conflicts with previously-created destinations that share the same name.
- Open the file with a text editor and add the following line:
- Save the file.
API call method
To use API calls to modify the configuration file of an additional destination, perform the following steps:
- Call the WHM API 1
backup_destination_listfunction to retrieve the ID of the additional destination to which you wish to send system backups.
- Call the WHM API 1
backup_destination_setfunction and include the following parameters and values:
id— The ID that the
The system’s backup initialization logs to the
/usr/local/cpanel/logs/error_log file. The
error_log file points to the individual account package logs. For more information, read our cPanel & WHM Log Files documentation.