I am sick of the new backup system. I migrated to it, since it's safe to assume that the legacy system will be discontinued eventually. Nothing but problems.
1) servers that say they've successfully transported the backup to the remote server, and the file size differs by about 25GB from the server to the remote location. And I get no error message about that.
2) I have a servers where I get this message "Unable to send" to remote destination error message.
3) I'm not able to configure SFTP due to some crazy incompatibility, so I'm stuck with plain unsecure FTP. In all fairness, that bug fix has been released to the Current Tier.
5) With the new backup system, if I keep 1 backup locally , I need enough available disk space to keep 2 just momentarily, from the time the next days backup can finish, and remove the previous days backup. I totally get the logic, but it really sucks compared to the legacy system where it simply overwrote the current backup with the new one.
6) Additional to #5, if I keep only one backup, this thread seems to indicate that if pruning would work like it should, the remote side would also only have one backup. This sucks as well. In legacy I used to keep 1 backup on the server, not 2, and then a script copied the files to the backup server, and it was set to keep 7 days worth of retentions. That doesn't seem possible anymore. I had full backups, of each of the previous 7 days on the remote server, ready to restore from.
7) Pruning isn't working, and I'm not convinced that I want it to start working . . . see #6
8) There's not a lot about this backup system to love other than it's more user-friendly. I'd actually choose one that works.
9) Why fix what ain't broke
10) Sick of this hassle
11) just want it to work, so I don't need to check my backups every day to verify the integrity
12) this is basic stuff to be getting wrong
13) sorry cPanel . . . I guess that's my feedback on this specific feature.