How to Fix cPanel/WHM Scheduled Backup Not Running (Cron Not Triggering)

Navigate to WHM > Backup > Backup Configuration.

At the top of the page you will see a Backup Status section. Confirm it is set to Enabled. If it says Disabled, enable it and click Save Configuration.

grep -i "BACKUPENABLE" /var/cpanel/backups/config

If the output is BACKUPENABLE=no, backups are disabled. Set it to yes directly or use the WHM UI to re-enable.

In WHM > Backup Configuration > Scheduling and Retention, look at the Backup Days row. If no days are ticked, the cron will never trigger a backup run.

The Backup Type field controls what kind of backup runs (Compressed, Uncompressed, or Incremental). If this was changed to Disabled, the system will skip the job even though Status is Enabled.

cat /var/cpanel/backups/config | grep -E "BACKUPDAYS|BACKUPTYPE"

A correctly configured server should show something like:

BACKUPDAYS=1,2,3,4,5
BACKUPTYPE=compressed

If BACKUPDAYS is empty or BACKUPTYPE=disabled, fix these values in the WHM UI and save.

df -h

Look at the partition where your backup destination lives (often /home or a mounted drive).

In WHM > Backup Configuration > Additional Destinations (or the main config section), find the Minimum Free Space option. The default is 1024 MB. If your available disk space is below this value, WHM will skip the backup.

grep "MINFREE" /var/cpanel/backups/config

Either remove old backup archives manually:

ls -lhS /backup/ | head -20
rm -f /backup/cpbackup/weekly/old-archive.tar.gz

Or increase your disk capacity. Lowering the MINFREE threshold without addressing the underlying disk space issue is a short-term workaround only.

ls -lt /usr/local/cpanel/logs/cpbackup/ | head -10

tail -100 /usr/local/cpanel/logs/cpbackup/$(ls -t /usr/local/cpanel/logs/cpbackup/ | head -1)

• Insufficient disk space — confirms the disk threshold issue from Section 3
• Backup is disabled — confirms the toggle issue from Section 1
• Transport failed — points to a remote destination connectivity problem (see Section 7)
• Lock file exists — indicates a stuck backup process (see Section 5)
• Permission denied — backup directory has wrong ownership

Fix the directory permission issue with:

chown -R root:root /backup
chmod 711 /backup

ps aux | grep cpbackup | grep -v grep

If this returns nothing but backups are still not running, a stale lock file is likely the culprit.

ls -la /var/cpanel/backups/*.lock 2>/dev/null
ls -la /tmp/.cpbackup* 2>/dev/null

rm -f /var/cpanel/backups/*.lock

/usr/local/cpanel/bin/backup --force

Watch the log file in real time to confirm the job starts:

tail -f /usr/local/cpanel/logs/cpbackup/$(date +%Y-%m-%d).log

grep -i "cpbackup\|backup" /etc/crontab
grep -i "cpbackup\|backup" /var/spool/cron/root

You should see a line similar to:

0 2 * * 1,2,3,4,5 root /usr/local/cpanel/bin/backup

systemctl status crond
# or on some distros:
systemctl status cron

If cron is stopped, start it:

systemctl start crond && systemctl enable crond

If the cron entry is missing, saving any change in WHM > Backup Configuration will regenerate it. Alternatively, run:

/usr/local/cpanel/scripts/rebuildhttpdconf
/usr/local/cpanel/bin/backup --force

Go to WHM > Backup Configuration > Additional Destinations, click your destination, then click Save and Validate Destination. WHM will test the connection and report any errors.

ls /var/cpanel/backups/*.backup_destination
cat /var/cpanel/backups/your_destination.backup_destination

If backups time out before completing, increase the transport timeout. Edit the relevant transport module or use WHM to adjust the Maximum Destination Timeout setting (default: 7200 seconds).

curl -v https://s3.amazonaws.com/your-bucket-name/ 2>&1 | head -20

iptables -L OUTPUT -n | grep -E "DROP|REJECT"

An outbound firewall rule blocking the FTP or SFTP port will silently kill all remote backup transfers.

If you need expert help diagnosing complex backup failures or setting up a reliable backup architecture, CloudHouse's managed server support team can audit your entire backup configuration and ensure your data is protected 24/7.