You are not logged in.
If you start a OneDiff backup for the first time and this first copy gets interrupted, and you start a new OneDiff backup, an error will be raised in the console, but the error will not be reported in the e-mail. We are working on it and will release an update soon.
Please, note that for this situation to become a problem, you would first need to ignore the first copy error when the process was interrupted.
Last edited by Daniel (2017-05-13 10:24:34)
We are working to make OneDiff much more robust, so that when any problem is detected, the OneDiff cycle is automatically re-initialized. This way you will be able to even program looped OneDiff backups that always keep a remote copy up to date.