"backup" interferes with "cpbackup"
I run backup (every Saturday) and cpbackup (every Wednesday) and I know they don't interfere with each other but I get this email notification every Wednesday even if backup is not suppose to run yet:
"The backup was not able to be completed because it timed out waiting for /scripts/cpbackup to finish"
It appears to me that the daily cron of backup is causing this message.
-
Hello, This is normal, as only one backup script can run at a time. You would notice the following message if you tried to run the new backup script when the legacy script is running: [2015-04-15 13:34:50 -0500] warn [backup] The other backup type is running as evidenced by the existence of: /var/cpanel/backuprunning [2015-04-15 13:34:50 -0500] info [backup] backup is waiting for the other backup to complete
You can modify the cron job for the new backup script so it does not run on Wednesdays (it runs every night by default even if it does not generate backups every night). Thank you.0 -
This is indeed a workaround but I think a better solution is: the backup will not execute at all since it's stated in the setting to only run on Saturday. So if Cron runs, it should check if it's actually Saturday first before it even attempts to send the email notification about the conflict. 0 -
This is indeed a workaround but I think a better solution is: the backup will not execute at all since it's stated in the setting to only run on Saturday. So if Cron runs, it should check if it's actually Saturday first before it even attempts to send the email notification about the conflict.
It's by design the backup script runs every night and checks to see if backups are required for that date. You are welcome to submit a feature request for a change in this behavior via: Submit A Feature Request Thank you.0 -
Hmm, I think this is more of a bug than a feature change. I understand that it currently runs every night but the issue on my case scenario is it should not send a notification because backup wasn't suppose to run anyway on that day regardless if cpbackup was running alongside or not. 0 -
The current behavior is by design and thus a feature request is required to see a change in the product. Backups are supposed to run every day by default, even if account backups are not generated. The script must run to determine if backups are required for the day.That being said, you can update the cron job so that it does not run on particular days. Thank you. 0
Please sign in to leave a comment.
Comments
5 comments