For cPanel & WHM version 68
What are my backup options?
You can use either of our two backup systems:
- WHM's Legacy Backup Configuration interface (WHM >> Home >> Backup >> Legacy Backup Configuration),
- WHM's Backup Configuration interface (WHM >> Home >> Backup >> Backup Configuration).
Both interfaces allow you to configure how automatic backups run on your server.
This FAQ focuses on the Legacy Backup Configuration system.
What does a backup store?
By default, backups only include system files and directories. When you enable account backups, they copy and store accounts' home directory contents, databases, email filters and forwarders, and DNS records. Enable account backups with the Backup Accounts option in the Legacy Backup Configuration interface (WHM >> Home >> Backup >> Backup Configuration).
Which files does a cPanel user's backup include?
After you enable account backups, the backup process runs as the cPanel user who owns the backup data. The system does not back up anything that a user does not own and cannot access.
- The system includes all of the files that the user owns in the backup.
- The system includes any files that the user does not own but has access to in the backup.
Can I select specific user accounts to back up?
Yes. Select specific user accounts to back up with the Select Specific Users option in the Legacy Backup Configuration interface (WHM >> Home >> Backup >> Backup Configuration). To do this, perform the following steps:
- Click Select >>.
- In the Legacy column, set the Backups column to On for specific users.
- Click Save.
How can I use rsync with a cPanel backup?
We do not support a backup procedure that uses
rsync. While it is possible to use the
rsync script with cPanel backups, we strongly recommend that you use our tools to ensure reliable backups. Under certain conditions, the
rsync script may corrupt SQL database backups.
How do backups handle DNS zones?
If you use a DNSONLY cluster, the
pkgacct script examines all of the DNS zones in the DNS cluster to find the record with the newest serial number. It then stores that DNS zone in the backup.
Which scripts run backups?
The following scripts run backups:
Where can I find backup logs?
The system stores backup logs in the
Where does the system store backups?
We strongly recommend that you do not perform backups to remote filesystems (for example; NFS, CIFS, smbfs, or other types of network drive systems). While you can store a backup directly to a remote filesystem, cPanel & WHM does not support this configuration. We strongly recommend that you work with a qualified system administrator to manage this custom backup path to avoid potential risks.
Select the location in which to store backups in WHM's Legacy Backup Configuration interface (WHM >> Home >> Backup >> Legacy Backup Configuration).
To select the location in which to store backups, perform the following steps:
- Navigate to WHM's Legacy Backup Configuration interface (WHM >> Home >> Backup >> Legacy Backup Configuration).
In the Backup Destination text box, enter the location in which to store the backups.
Use a directory, network filesystem, or coda mount with at least twice the space of your
/homedirectories or partitions. Do not set this value to your
/homedirectory or partition.
- Click Save to save your changes.
What does cPanel & WHM back up when I select configuration files? Where can I find the backups?
When you back up configuration files, the system automatically stores them in the
files directories. When you back up the entire MySQL directory, the backup stores its contents in the
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.
Can I run backups to locally mounted remote filesystems?
- If you use a mounted filesystem to store backups, we strongly recommend that you mount the system with the
noexecoption. If you pass the
noexecparameter to the
mountparameter, the binaries cannot run on the mounted filesystem.
- We strongly recommend that you do not perform backups to remote filesystems (for example; NFS, CIFS, smbfs, or other types of network drive systems). While you can store a backup directly to a remote filesystem, cPanel & WHM does not support this configuration. We strongly recommend that you work with a qualified system administrator to manage this custom backup path to avoid potential risks.
noexecoption by default. To do so, edit the
/etc/fstabfile. This file contains a list of mountable file systems and their configuration options.
To configure a mountable file system that automatically uses the
noexec option, edit its entry in the
/etc/fstab file to resemble the following example:
Users who wish to mount or unmount a partition must place the partition in the
/etc/fstab file. The backup utility only mounts or unmounts partitions that appear in the
The example above describes the following configuration options:
|Device||Default mount point||file system type||Mount options||Dump option||fsck order|
To remount a backup disk while the system boots, run the following command:
How does cPanel & WHM determine when to run backups?
If you run the
/usr/local/cpanel/scripts/cpbackup script without the
--force option, then the following are true:
- cPanel & WHM creates a monthly backup if the existing monthly backups are more than 29 days old.
- cPanel & WHM creates a weekly backup if the existing weekly backups are more than six days old.
cPanel & WHM creates a daily backup if the existing daily backups are more than 12 hours old.
If backups require more than 12 hours to run, they will skip a day.
Can I manually edit my backup schedule?
Automatic backups run via a cronjob. Edit the crontab to control when backups run. The
/usr/local/cpanel/scripts/upcp script does not overwrite this cronjob. Perform this action via SSH as the
root user with the
crontab -e command.