This object is in archive!
Legacy local backup
Needs Review
The normal backup allows us to save our backup both in a remote FTP server and locally.
You should definitely enable this for Legacy backups as well! Support department told me that we have to request it in order to be added. Spread this out, because I own a Joomla website with phpbb forum, the database, files, mysql, are way too huge (backup over 20GB) and they can only be saved with Legacy backup. So my backup is not saved locally.
I like this idea 
cPanel, WebHost Manager and WHM are registered trademarks of cPanel, L.L.C. for providing its computer software that facilitates the management and configuration of Internet web servers.
As the name implies, the Legacy Backup feature will not receive further new features (although still eligible for bug fixes/etc). The intention is to eventually negate the need for the legacy backup feature entirely and then remove it from the product.
Of course this requires that the new backup system be more favorable and provide the same (or better) solutions than the legacy backup system. You seem to suggest in your reply that the new backup system has difficulties with a certain threshold of account sizes. I would strongly suggest further reaching out to our support staff (it sounds like you've already discussed the legacy backup system with them) and raising those concerns. What you describe sounds like a bug in the new backup system and we would want to tackle it as such.
If there are any further criteria beyond bugs (which should be reported to support) that you would need the new backup system to support before you could abandon the legacy one, I strongly encourage filing feature requests for them as well.
As advised, the eventual goal is to deprecate and remove the legacy backup system once the new backup system can accommodate appropriately. There will not be new feature development for legacy features.
As the name implies, the Legacy Backup feature will not receive further new features (although still eligible for bug fixes/etc). The intention is to eventually negate the need for the legacy backup feature entirely and then remove it from the product.
Of course this requires that the new backup system be more favorable and provide the same (or better) solutions than the legacy backup system. You seem to suggest in your reply that the new backup system has difficulties with a certain threshold of account sizes. I would strongly suggest further reaching out to our support staff (it sounds like you've already discussed the legacy backup system with them) and raising those concerns. What you describe sounds like a bug in the new backup system and we would want to tackle it as such.
If there are any further criteria beyond bugs (which should be reported to support) that you would need the new backup system to support before you could abandon the legacy one, I strongly encourage filing feature requests for them as well.
As advised, the eventual goal is to deprecate and remove the legacy backup system once the new backup system can accommodate appropriately. There will not be new feature development for legacy features.
As the name implies, the Legacy Backup feature will not receive further new features (although still eligible for bug fixes/etc). The intention is to eventually negate the need for the legacy backup feature entirely and then remove it from the product.
Of course this requires that the new backup system be more favorable and provide the same (or better) solutions than the legacy backup system. You seem to suggest in your reply that the new backup system has difficulties with a certain threshold of account sizes. I would strongly suggest further reaching out to our support staff (it sounds like you've already discussed the legacy backup system with them) and raising those concerns. What you describe sounds like a bug in the new backup system and we would want to tackle it as such.
If there are any further criteria beyond bugs (which should be reported to support) that you would need the new backup system to support before you could abandon the legacy one, I strongly encourage filing feature requests for them as well.
As advised, the eventual goal is to deprecate and remove the legacy backup system once the new backup system can accommodate appropriately. There will not be new feature development for legacy features.
As the name implies, the Legacy Backup feature will not receive further new features (although still eligible for bug fixes/etc). The intention is to eventually negate the need for the legacy backup feature entirely and then remove it from the product.
Of course this requires that the new backup system be more favorable and provide the same (or better) solutions than the legacy backup system. You seem to suggest in your reply that the new backup system has difficulties with a certain threshold of account sizes. I would strongly suggest further reaching out to our support staff (it sounds like you've already discussed the legacy backup system with them) and raising those concerns. What you describe sounds like a bug in the new backup system and we would want to tackle it as such.
If there are any further criteria beyond bugs (which should be reported to support) that you would need the new backup system to support before you could abandon the legacy one, I strongly encourage filing feature requests for them as well.
As advised, the eventual goal is to deprecate and remove the legacy backup system once the new backup system can accommodate appropriately. There will not be new feature development for legacy features.
Replies have been locked on this page!