Heads Up! Legacy Backups are no longer running!

anoopk350

Well-Known Member
May 6, 2020
73
9
8
Kochi
cPanel Access Level
Root Administrator
Deprecated the Legacy Backup system in cPanel & WHM version 64 and its removed in cPanel & WHM version 80.
 

schoeps

Well-Known Member
Sep 22, 2004
87
7
158
yes, but you can add them, back, I think the triggers were removed from the global cron
 

schoeps

Well-Known Member
Sep 22, 2004
87
7
158
why. There are many users that use that system and the current backup system lacks an alternate scheduling. For folks that may not read the change logs, you could potentially be giving a false sense of security. I understand that you are moving away form this system, but there should be a suitable replacement in place, I have been relying on it for over 8 years on 20+ servers!
 

cPanelLauren

Product Owner
Staff member
Nov 14, 2017
13,296
1,252
313
Houston
I see two separate cases related to this being removed CPANEL-32780 and CPANEL-32945 - both of which are resolved in v90 removing the cron for the legacy backup system.

Both cases are noted here:

We've had the legacy backup system deprecated for several years now at this point you should not be relying on it remaining in the product as it will be removed completely.

The current backup system has been in place for some time now and if it is not suitable or does not meet your needs I'd not only urge you to explain what it is, it doesn't do but also open a feature request for it using the link in my signature.

Furthermore, there are other alternatives such as JetBackup which are more versatile and may provide more of the functionality you're looking for.
 

schoeps

Well-Known Member
Sep 22, 2004
87
7
158
I understand, oh well. Spent a good bit of yesterday working on the AWS S3 integration on a couple of boxes to find some random :Unable to send “/backup/2020-08-11/accounts/xxxx.gz” to destination “AWS S3 Bucket”:" Oh well.
 

plague

Well-Known Member
Sep 22, 2006
75
17
158
Brasil
cPanel Access Level
Root Administrator
Twitter
Hello @cPanelLauren

Now that the legacy system has been wiped out, how can we avoid the new system requiring double the disk space for cpanel backup?
Is there a way to accomplish the same behavior as the legacy backup in the new backup (removing the account old backup BEFORE the new one is created)?

I mean, if you have 1TB backups you need a 2TB disk, because in the second day the second backup will consume another 1TB until it finishes and the old backup is removed.

I know that Incremental backups can solve that, but incremental backup is too limited when it comes to remote destinations.
 

schoeps

Well-Known Member
Sep 22, 2004
87
7
158
It's probably one of the most important features and it's a mess. I get a feeling they would rather push "JetBackup" than just address some simple to implement concepts like what you had mentioned or just adding schedules to the remote backups.
 

cPanelLauren

Product Owner
Staff member
Nov 14, 2017
13,296
1,252
313
Houston
Hey guys,

I have something of a workaround for you for now, but I cannot stress it enough, that the Legacy system is going away and you must be looking at alternatives. The space issue is not something that is going to be changed in the current backup system from what I understand after speaking to the product owner for that feature. The workaround to use the legacy system would be the following:

Code:
echo “BACKUPENABLE yes” > /etc/cpbackup.conf
And re-add the cron to the cron manager.

It was just the cron that was removed not the actual code for the legacy backup system.

I do hope that helps for now, but this is not a permanent solution.