Erratic backup
We facing inconsistencies/errors in the backup schedule:
1. The backup is scheduled to run from Saturday but it ran for a about a day then stopped. We assumed it had finished but today (Monday) we see the job is continuing
2. We have users whose backup is turned off but we can see they are being backed up.
What could be the problem?
-
Hello, Could you check to see if any existing backup processes are still running? EX: ps aux|grep tar ps aux|grep backup
You can also review the backup log in /usr/local/cpanel/logs/cpbackup/ to see the most recent output. Thank you.0 -
For last 3 weeks the backups have not completed. They start then stop. It has been happening for weekly backups but yesterday we saw even monthly backup affected. Though the logs show the backup completed successfully only a few accounts are being backed up. We are also not getting the email we have been been receiving whenever backup completes. The last backup log shows an error at the beginning of the backup but the backup seems to continue then stops after some time: AT THE BEGINNING: [2016-12-01 02:00:02 +0100] info [backup] Setting I/O priority to reduce system load: unknown: prio 0 [2016-12-01 02:00:02 +0100] info [backup] Hard Linking available on "/backup" [2016-12-01 02:00:02 +0100] info [backup] Running dir & file backup with target : /backup/monthly/2016-12-01/system /usr/bin/gtar: Removing leading `/' from member names /usr/bin/gtar: Removing leading `/' from member names /usr/bin/gtar: Removing leading `/' from member names /usr/bin/gtar: Removing leading `/' from member names /usr/bin/gtar: Removing leading `/' from member names /usr/bin/gtar: Removing leading `/' from hard link targets /usr/bin/gtar: Removing leading `/' from member names /usr/bin/gtar: Removing leading `/' from member names /usr/bin/gtar: Removing leading `/' from member names /usr/bin/gtar: Removing leading `/' from member names /usr/bin/gtar: Removing leading `/' from member names /usr/bin/gtar: Removing leading `/' from hard link targets /usr/bin/gtar: /var/cpanel/bandwidth.cache: file changed as we read it [2016-12-01 02:03:10 +0100] warn [backup] (XID ttp3qj) <80><9C>/usr/bin/gtar<80><9D> ended prematurely because it received the <80><9C>PIPE<80><9D> (13) signal: at /usr/local/cpanel/Cpanel/Backup/Utility.pm line 218. AT THE END: [2016-12-01 05:59:55 +0100] homefiles is: 10810 [2016-12-01 05:59:55 +0100] pkgacct completed [2016-12-01 05:59:56 +0100] info [backup] Queuing monthly backup copy for transport [2016-12-01 05:59:56 +0100] info [backup] Queuing transport of file: /backup/monthly/2016-12-01/accounts/philipmu.tar.gz 0 -
[2016-12-01 02:03:10 +0100] warn [backup] (XID ttp3qj) <80><9C>/usr/bin/gtar<80><9D> ended prematurely because it received the <80><9C>PIPE<80><9D> (13) signal: at /usr/local/cpanel/Cpanel/Backup/Utility.pm line 218.
Feel free to open a support ticket using the link in my signature so we can review the backup logs and take a closer look at the system. You can post the ticket number here and we will update this thread with the outcome. Thank you.0 -
Support Request ID: 8032903 This week's backup job is already under progress. As a way to replicate the problem it might be an opportune time to monitor if it abruptly stops. 0 -
Hello, To update, it looks like the backup failures were the result of some accounts reaching their disk space limit, in addition to some database corruption/missing databases. Thank you. 0 -
The problem was with erroneous security settings, in the file /etc/security/limits.conf 0
Please sign in to leave a comment.
Comments
6 comments