You can use either of our two backup systems:
Both interfaces allow you to configure how automatic backups run on your server.
This FAQ focuses on the Legacy Backup Configuration system.
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).
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.
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:
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.
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.
The following scripts run backups:
The system stores backup logs in the
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:
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
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
You can configure a file system to use the
noexec option by default. To do so, edit the
/etc/fstab file. 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:
/dev/sda5 /backup ext3 defaults,noexec 0 0
Users who wish to mount or unmount a partition must enter the partition 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:
mount -o remount,noexec /backup
If you run the
/usr/local/cpanel/scripts/cpbackup script without the
--force option, then the following are true:
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.
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.