Why i find FTP Destinations Disabled in WHM New Backup system?

i don't really care about emails alerting me about disabled backups

the backup destination should not disable under ANY circumstance!!!!

the same ftp destination is working perfectly with the old backup sistem in parallel, however the new one just kicks the bucket from time to time and stops making backups forever and ever until manual intervention. this is really illogical as now you need to do daily backup reactivations and a lot of wasted time.

there MUST be an option: "NEVER DISABLE THIS BACKUP DESTINATION, UNDER ANY CIRCUMSTANCE, EVEN IF HOSTNAME IS TOTALLY MISSING"

 

the error seems to be that it does not find the file to upload:

so it disables the entire remote backup destination because of missing local file. VERY LOGICAL.

- - - Updated - - -

also this problem exists for months, not sure why such an important and vital module does not get corrected faster

 

I've got to be fair, we are seeing it disable itself sometimes so we have to re-enable it again afterwards. Nothing wrong with the destination FTP server at all and you can always re-validate it immediately. We could do with a fix for this or as mentioned, an option to stop disabling the backup destinations

 

Begin a backup the main concern is reliablility. WHM/Cpanel created a HUGE workload having to verify backup destinations on several servers and having to renable them once a week.

The old backup still runs in parallel and does it's work each day. The new backup, with the same FTP login and destination occasionally needs to be reenabled.

I am finding 2 MAJOR outpoints with the new backup:
- totally unreliable (compared to the other old one), even if there is a total failure today with the backup server, the next day should continue as usual, now i have to manually check all servers to validate. Backup destinations should NEVER deactivate, ever, under any circumstance.
- second major outpoint is not keeping a backup of terminated accounts. Very rarely (2-3 times a year) we had to recover an account that was terminated. with the new backup system, the folder names being named after the backup date, it just erases any backup that is more than 1 month old (if monthly is enabled) forcing us to manually back up any account that we wish to terminate.

the above 2 flaws seriously counterbalance any speed gain and pluses offered by implementing pigz

Is there noone else with these problems that they were not raised and remedied much faster?