This issue cost me a lot of time and effort, but at least I found the solution, so in case it could help:
- I have set-up a remote backup on another location and it works ok.
- I have found that some remote back-up jobs do not work, the job is created and as soon as that it is completed (i.e. new share will only use 4KB and remain empty) while other jobs work fine.
Turns out the issue is in some characters in the source share name not being supported by the remote backup functionality, and it being a poor interface (sorry but it cannot allow editing a job?! and it seems this is since years…): you do not get notified that the job is not working.
Changing share name to something with only alphabetical characters solves the issue.