Why are there two different backup entries in crontab?

electric

Well-Known Member
Nov 5, 2001
742
5
318
Hello,

The crontab for all our servers have two different backup entries:


Code:
15 0 * * * /usr/local/cpanel/scripts/cpbackup
0 2 * * * /usr/local/cpanel/bin/backup
Are both of these necessary? If not, which one is the correct entry?

(We are using the "new" backup system and have disabled the legacy system.)

Thanks.
 

quietFinn

Well-Known Member
Feb 4, 2006
1,071
32
178
Finland
cPanel Access Level
Root Administrator
Hello,

The crontab for all our servers have two different backup entries:


Code:
15 0 * * * /usr/local/cpanel/scripts/cpbackup
0 2 * * * /usr/local/cpanel/bin/backup
Are both of these necessary? If not, which one is the correct entry?

(We are using the "new" backup system and have disabled the legacy system.)

Thanks.
The 1st one ("cpbackup") is for the legacy backup, and if legacy backup is disabled it does nothing.
 

cPanelMichael

Technical Support Community Manager
Staff member
Apr 11, 2011
47,911
2,233
363
cPanel Access Level
DataCenter Provider
Twitter
Hello :)

Yes, it's normal to see both entries. The "/scripts/cpbackup" entry is for legacy backups and the "/usr/local/cpanel/bin/backup" entry is for the new backup system. Note that the existence of the cron job does not mean backups are enabled. The scripts make that determination each time they run.

Thank you.
 

electric

Well-Known Member
Nov 5, 2001
742
5
318
The "/scripts/cpbackup" entry is for legacy backups and the "/usr/local/cpanel/bin/backup" entry is for the new backup system.
Are you sure this is not reversed? As a test, I removed both backup entries from the crontab. Then I went into WHM and clicked the "Configure cPanel Cron Jobs" link and set the backup cron job to run at 00:15. Now I only have one cron job listed in crontab:

15 0 * * * /scripts/cpbackup
In WHM, I have disabled legacy backups, and have enabled the new backup system.

So it seems something is not right somewhere? Let me know what you think...
 

electric

Well-Known Member
Nov 5, 2001
742
5
318
It's because "Configure cPanel Cron Jobs" does not support the new backup system (yet).
Ah, I forgot.. this is cpanel... I should have expected that. :rolleyes:

If anyone from cpanel is reading this, you might possibly want to maybe perhaps consider adding a note in the WHM modify cron page that explains this backup cron is ONLY for the old legacy backup system.

:)
 

electric

Well-Known Member
Nov 5, 2001
742
5
318
Hello,

Please feel free to open a feature request for that at cPanel Feature Requests.
Seriously? You work for cpanel, right? Well, if you think this is something that would benefit *your* customers, then go for it. My posting into the features request is just going to get buried under the 300 other requests. People aren't going to use their votes to raise this one to the top, so it won't be implemented due to massive user demand, that's for sure. The only way this has a chance to get put into prod is if someone working at cpanel says, "Ya.. that makes sense. Duh."
 

cPanelMichael

Technical Support Community Manager
Staff member
Apr 11, 2011
47,911
2,233
363
cPanel Access Level
DataCenter Provider
Twitter
Hello :)

A feature request is actually not necessary in this case because the cron job for the new backup system is going to be added to the "Cron Config" plugin in cPanel version 11.42 per internal case 85381.

Thank you.