[Feature] Error: dump users_database failed ---> Backup should continue and write in an error.log file!

[DeRaja]

Describe the feature or change in detail

Hello!

For some reason, which I can explaiin in details, the database under the mysql dir was removed due to a mysql restore function. Siince then, the Hestia scripts refused to make backups of the user's databases and declared one database in the flat config file does not exists.

Now, if one database is missing, why should the entire backup fail?

The request is to circumvent a non-existent database and continue the backup of the user. If such an error is found, then it should make a seperate error log, which cannot be overwritten in the normal user.log file. Only then the admin can determine when and what happened at a later date because the user.log file will be overwritten upon successful creation of a tar file.

Would you like to sponsor this feature to have it implemented?

No