Skip to content

Scheduling cPanel backups in WHM — daily, weekly, monthly retention that actually fires

How to set the backup schedule in WHM Backup Configuration — the daily/weekly/monthly cadence, retention counts, and the timing choices that decide whether backups finish before traffic returns.

cPanel’s built-in backup system is configured almost entirely from one screen, and the schedule is the part people set once and never revisit — which is exactly why so many servers run backups that overlap the morning traffic peak, keep too few copies to recover from a Tuesday mistake discovered on Friday, or quietly stopped firing months ago. Getting the cadence and retention right in Backup Configuration is what turns “we have backups” into “we can restore the version we actually need.”

What’s happening

WHM » Backup » Backup Configuration writes to /var/cpanel/backups/config and drives cPanel’s backup runner (the backup system that replaced the legacy cpbackup). It has three independent retention buckets: Daily, Weekly, and Monthly. Each can be enabled separately, each keeps its own number of copies, and the Daily bucket lets you pick which days of the week it runs. cPanel rotates within each bucket — keep “5” daily and the sixth night’s backup pushes out the oldest, so retention is a count, not an age.

The runner is triggered by cron (cPanel’s own /etc/cron.d/cpbackup entry, by default early morning). The actual start time is governed by the cron entry and cPanel’s backup window; the duration depends on total account size, compression, and destination throughput. On a busy server those two facts collide: a backup that starts at the default hour but runs long can still be hammering disk and I/O when the business day begins. The schedule you set is therefore not just “which days” but “started early enough, with enough retention in each bucket, to finish before traffic and to cover the gap between when a problem happens and when someone notices.”

How to verify

See the current backup configuration and what is actually scheduled:

# The live backup config (retention, buckets, enabled state)
cat /var/cpanel/backups/config
whmapi1 backup_config_get

# The cron entry that triggers the run, and its time
cat /etc/cron.d/cpbackup

Confirm backups are genuinely running and when the last ones completed:

# Backup runner logs — start, finish, per-account results
ls -lt /usr/local/cpanel/logs/cpbackup/ | head
tail -60 /usr/local/cpanel/logs/cpbackup/$(ls -t /usr/local/cpanel/logs/cpbackup/ | head -1)

Check what backups exist on disk and their dates, per bucket:

# Local backup destination contents by date
ls -la /backup/ 2>/dev/null
ls -la /backup/daily /backup/weekly /backup/monthly 2>/dev/null | head -40

The fix / steps

  1. Enable all three buckets with deliberate counts. In Backup Configuration turn on Daily, Weekly, and Monthly and set a retention count for each — a common shape is several daily, a few weekly, a couple of monthly. The point of three buckets is depth: dailies cover recent mistakes, weeklies cover the “discovered it Friday” gap, monthlies cover slow-burn corruption no one noticed for weeks.
  2. Pick daily run days to match recovery needs, not habit. The Daily bucket lets you choose days of the week. Running every day gives the finest recovery granularity; skipping days saves space at the cost of a coarser timeline. Choose based on how much change a day of data loss represents for these accounts, not on a default.
  3. Set retention as a count and size the disk for it. Each bucket keeps N copies and rotates the oldest out. More retention means more disk: total backup space is roughly (sum of account sizes) × (copies kept, accounting for incrementals/compression). Confirm /backup (or the destination) has room for the full rotation before raising counts, or the run fills the disk and fails.
  4. Start the run early enough to finish before traffic. The default cron time may not leave enough window on a large server. Move the start earlier (edit the schedule/cron) so the run completes before the business day, and stagger it away from other heavy jobs (updates, log rotation). A backup still running at peak competes with live traffic for disk and I/O.
  5. Choose compression with the time/space trade-off in mind. Compressed backups save destination space but take longer and use more CPU during the run; uncompressed finish faster but need far more room. On a tight backup window, compression can be what pushes the run into business hours — match the setting to whether time or space is the binding constraint.
  6. Confirm the destination is configured, not just local. A schedule that writes only to local /backup is one disk failure from no backups. In Backup Configuration » Additional Destinations add an offsite target so the schedule copies there too. The cadence is only as good as where it lands — local-only retention does not survive losing the server.
  7. Set who is backed up. Backup Configuration controls whether all accounts or a selected set are included, and whether suspended accounts are backed up. Decide deliberately — excluding suspended accounts saves space but means a suspended-then-needed account has no recent copy. Confirm the account list matches what you actually need protected.
  8. Verify the schedule fires and finishes, then re-check periodically. After saving, wait for the next run and read /usr/local/cpanel/logs/cpbackup/ — confirm it started on time, completed, and produced files in each bucket. A schedule that silently stopped (disk full, config drift, a cron removed by another tool) looks identical to a working one until you need a restore. Check the logs on a cadence, not only after an incident.

A backup schedule is only real once you have confirmed it fires on time, keeps enough copies in each bucket, and lands somewhere off the server. Stack Harbor configures and monitors cPanel backup schedules and retention under managed cPanel operations — start a conversation to make sure your backups are actually running.