Backup not completed ?

kernow

• November 04, 2013 04:03

Running the new backup script, were getting emails from cpanel saying "The backup was not able to be completed because timed out waiting for /bin/backup to finish" However the backup is still running and we get the normal email later in the day saying its completed. We notice in the root crontab both old and new backup scripts are listed: /usr/local/cpanel/bin/backup /usr/local/cpanel/scripts/cpbackup Is this the problem? should one (legacy) be removed?

• 

  ravi9

  • November 04, 2013 09:35

  you should use either legacy or the new backup system. I personally like the new backup.

  0
• 

  kernow

  • November 04, 2013 09:50

  [quote="ravi9, post: 1496542">you should use either legacy or the new backup system. I personally like the new backup.
  That's not the question.

  0
• 

  cPanelMichael

  • November 04, 2013 14:20

  [quote="kernow, post: 1496531">We notice in the root crontab both old and new backup scripts are listed: /usr/local/cpanel/bin/backup /usr/local/cpanel/scripts/cpbackup Is this the problem? should one (legacy) be removed?
  It's safe to remove the legacy backup cron job if you no longer use it. However, it's existence should not be an issue if legacy backups are disabled. The cron job will detect that legacy backups are disabled and it will not generate any backup archives. Thank you.

  0
• 

  kernow

  • November 04, 2013 14:57

  [quote="cPanelMichael, post: 1496762">The cron job will detect that legacy backups are disabled and it will not generate any backup archives. Thank you.
  That's what we thought, so is there anything else that could cause that error message? Update. It maybe the cron job. I believe that /usr/local/cpanel/scripts/cpbackup is the cron for legacy? but were using the newbackup system. A few days ago we edited the backup cron job from WHM ( we would normally use CLI) to alter the time by 2 hours but we now see it changed the time for the legacy backup not the cron for new /usr/local/cpanel/bin/backup so it maybe a bug?

  0
• 

  cPanelMichael

  • November 04, 2013 15:49

  I don't believe the legacy backup script (/scripts/cpbackup) is responsible for this issue if you have them disabled. Do you notice any errors in the backup logs located in /usr/local/cpanel/logs/cpbackup for the date the warning message was sent out? Also, have you reproduced the issue since then? Thank you.

  0
• 

  kernow

  • November 04, 2013 19:52

  Hello, No errors reported today in /usr/local/cpanel/logs/cpbackup However, from the CLI I just edited the cron for /scripts/cpbackup to start @ 2am. Now, if we look in WHM cron jobs the backup has changed to 2.am which shouldn't have happened as were using the new backup script which uses /usr/local/cpanel/bin/backup and is set for 4am

  0
• 

  cPanelMichael

  • November 05, 2013 14:10

  The "/usr/local/cpanel/bin/backup" cron job is currently not available in the "Cron Config" plugin page. There are plans to add this in a future build of cPanel, but there is no specific ETA on that at the moment. In the meantime, the workaround is to edit this cron job manually from the command line using the "crontab -e" command. Thank you.

  0
• 

  kernow

  • November 05, 2013 15:10

  Thanks for the info.

  0

Please sign in to leave a comment.