Deprecated the Legacy Backup system in cPanel & WHM version 64 and its removed in cPanel & WHM version 80.
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!
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:
docs.cpanel.net
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.
Both cases are noted here:
90 Change Log | cPanel & WHM Documentation
This document lists the cases and bugs worked on during the version 90 release cycle.
docs.cpanel.net
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.
The backup transport logs should provide you with further details on what occurred there. You can find them at
/usr/local/cpanel/logs/cpbackup_transporter/
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.
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.
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:
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.
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.confIt 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.
Same here, the legacy backup is working but upcp is removing it's cron entry and readding the new backup cron.
I just added "/scripts/cpbackup" on a /etc/cron.d/ cron file as a workaround.
From Lauren: "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."
I know this is an old thread, but I find legacy backups very useful because I back them up to a cloud-based system that keeps several versions. If I need to to restore a backup, it's really easy to do so from my cloud backup system. But, as long as pkgacct is available, I can use that and send those cp move files to the cloud.
I know this is an old thread, but I find legacy backups very useful because I back them up to a cloud-based system that keeps several versions. If I need to to restore a backup, it's really easy to do so from my cloud backup system. But, as long as pkgacct is available, I can use that and send those cp move files to the cloud.
