Investigating a failed WHM backup job

Collect the job time, affected account or destination and the complete failure notification. Check free disk space and confirm no backup or transfer is already running for the same scope.

1. As an authorised administrator, open the matching job log in /usr/local/cpanel/logs/cpbackup/ and locate the first relevant creation error. Match the job time and account before interpreting the entry.
2. For a remote-copy problem, inspect /usr/local/cpanel/logs/cpbackup_transporter as an authorised administrator. Separate a completed local archive from a failed remote upload.
3. Check account quota, server free space, destination credentials, path permissions and network reachability according to the error.
4. Correct the identified cause, then rerun only through the supported backup workflow at a time that will not overlap a production cycle.
5. Verify the resulting archive and remote copy, and perform a sample recovery check. Confirm alerts return to their expected healthy state.

The affected stage should complete and a usable recovery copy should exist. Retain older verified backups until the replacement is confirmed, particularly when retention settings could otherwise prune them.

If a process appears stuck, inspect its status and logs before terminating it. Do not delete arbitrary staging files belonging to an active job. A destination validation pass does not guarantee enough storage or time for the largest real archive.

Only when evidence shows a legitimate transfer or restore needs more time. Authentication failures, full disks and inaccessible paths will not be fixed by waiting longer.

• Validating a remote WHM backup destination
• Configuring WHM backups and retention for the available storage
• Checking WHM service status before restarting anything
• Restoring an account from a WHM backup

• cPanel: The cPanel Log Files
• cPanel: Backup Configuration