For cPanel & WHM 11.44
(Home >> Backup >> Legacy Backup Configuration)
This feature allows you to configure how your server creates and stores backup files. You can configure automatic backups, backup retention schedules, and backup storage locations.
This option allows you to specify whether the Legacy Backup feature is enabled, disabled, or only enabled for restorations:
Select the interval at which you wish to run automatic backups. You may select Daily, Weekly, or Monthly.
|Backup Retention||Select the backups that you wish to retain.|
|Days to Run Backup||Select the days on which you wish to run backups.|
|Remount/Unmount Backup Drive|
Select whether you wish to remount and unmount the specified backup drive while backups run.
To enable this option, you must have a separate drive, coda, or NFS) drive.(
|Bail Out If Backup Drive Mount Fails||Select whether you wish to cancel the backup process if the backup drive fails to mount.|
Enable this option if you wish to only back up and restore data that has changed.
You cannot enable this option with FTP backups. This option does not use file compression.
|Backup Accounts||Select whether you wish to back up accounts. If this option is disabled, the system will only back up system files. This option is disabled by default.|
|Compress Account Backups||Select whether you wish to compress backup files.|
|Backup Configuration Files|
Select whether you wish to back up configuration files.
Configuration files are not required to restore a backup.
|Backup SQL Databases|
You can choose the following options for this setting:
|Backup Access Logs||Select whether you wish to store access logs.|
|Backup Bandwidth Data||Select whether you wish to store bandwidth data.|
|Use local DNS zone files rather than retrieving the latest zone updates from the cluster.||Select Enabled to cause the |
You can choose the following options for this setting:
|EXPERIMENTAL: Use Hard Links for weekly and monthly backups to reduce disk usage and backup time.||Select whether you wish to use hard links for weekly and yearly backups.|
|EXPERIMENTAL: Enable use of optimized account backup tool.||This setting instructs the backup utility to use the |
|Remote FTP Host (Remote FTP Backup Only)|
If you opted to use Remote FTP backups, enter the remote FTP server's IP address in the Remote FTP Host text box.
When you specify the backup host, exclude the FTP protocol.
|FTP Backup User (Remote FTP Backup Only)||If you opted to use Remote FTP backups, enter the FTP account's username in the FTP Backup User text box.|
|FTP Backup Password (Remote FTP Backup Only)||If you opted to use Remote FTP backups, enter the FTP account's password in the FTP Backup Password text box.|
|FTP Backup Directory||If you opted to use Remote FTP backups, enter the directory in which you wish to store backup files.|
|FTP Backup Timeout||If you opted to use Remote FTP backups, enter the number of seconds of inactivity after which the FTP transfer will time out. This option defaults to |
|FTP Backup Passive Mode||If you opted to use Remote FTP backups, enable this option if the remote server is behind a firewall, or if FTP backups fail.|
|Backup Destination||If you use Standard backups, enter the directory in which you wish to store backups.|
|Select Specific Users||Click Select to select users whose accounts should be backed up automatically.|
When you have used these options to configure backups to your satisfaction, click Save.
More about hard links
Traditionally, our backup system copies and stores backup files in multiple locations. This means that for a period of time, your server has two identical files on the file system. Furthermore, when you copy and store a new file, it increases disk I/O significantly when you work with large accounts. Hard links aim to fix these issues.
A hard link is similar to a symlink but can make multiple references to a single inode. This allows our backup system to point a monthly or weekly backup file to an existing daily backup file (in accordance with your configuration), without the need to copy and store two different backup files. Ultimately, this prevents redundancies and reduces disk I/O.
Use a mounted file system
When you use a mounted file system to store backups, we strongly recommend that you mount the file system with the
noexec option. If you mount the file system with the
noexec option, binaries cannot run on the mounted file system.
You can configure a file system to use
noexec by default. To do so, you will need to edit the
/etc/fstab file. This file contains a list of mountable file systems and their configuration options. It is important to note that the backup utility will only mount or unmount partitions that appear in the
/etc/fstab file. To configure a mountable file system that will automatically use
noexec, 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
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 is booted, run the following command:
This command assumes that
/backup is already mounted.
Run backups manually
To run a backup manually, run the
If the backup is up-to-date and you wish to run backups anyway, run the
/usr/local/cpanel/scripts/cpbackup --force command.
A note about backups
The backup process runs as the cPanel user whose data it backs up. Anything a user cannot access is not backed up.
- The backup includes all of the files that the user owns.
- The backup includes files that the user does not own but that the user can access.
- The backup does not include files that the user does not own and cannot access — even if they are stored in the user's home directory.
Files that are owned by the user
nobody in the
public_html directory are not backed up when
cpbackup runs. Some third party software, such as phpBB, puts files in this directory. Files in this directory do not belong to a particular user. As a result,
cpbackup will ignore these files. To prevent this complication, manually backup any desired files in a cron job. You can then exclude these files from
For more information about backups, read our Legacy Backups FAQ