As per request, taken the issue #5669 here for discussion.
After experiencing several backup errors, and digging through the comunity to hopefully get them fixed, a few suggestions to make life a bit easier: • add a button to test connection to backup host and read/write permissions. This will take out the issue one has to wait until the next scheduled backup has been initiated before finding out weather or not it was successful. • For filesystems where applicable: add a minimum version combo box. This will ensure that for instance smb servers that have been configured to use protocol 2.0 (or higher) [netgear nas can do so] will receive the backup without throwing an error.The github original issue
As a side note I would also highlight that both issues have already been addressed: • Cockpit already has a "test connection" button for backupsUsing the current release, I don't see one, but I'll accept that might be in the next release. If cockpit is the web interface that is.
• CentOS 7.6 already negotiate the best Samba protocol when mounting CIFS resourcesBe that as it may, the reason why it's proposed is to align configurations of both nethserver and backup destination as best as possible. In my case, for instance, I know perfectly well that my nas won't accept smb connections below smb version 2.1 because I set it that way, and just in case nethserver for some reason would decide to use a rong version...