Maybe the full log gives the bigger picture.
IIRC when duplicity finds and error by default it does 5 retries before giving up. The IOError (Input / Output Error) could be a failure to access/read/write to the destination or to some file, for example.
If I’m not mistaken NethServer spits outs any error it receives and marks the task as failed even when a later retry has succeeded.
It looks incomplete but no reason or noted failure. The bold lines straight after dumping the DB tables and then claim success!! But data is there on the NAS.
Nov 5 23:16:59 srv-sb esmith::event[5167]: Event: post-backup-data backup-data
Nov 5 23:17:00 srv-sb esmith::event[5167]: Action: /etc/e-smith/events/post-backup-data/S20nethserver-backup-config-push2history SUCCESS [0.443726]
Nov 5 23:17:00 srv-sb esmith::event[5167]: Action: /etc/e-smith/events/post-backup-data/S50mysql-delete-dumped-tables SUCCESS [0.004996] Nov 5 23:17:00 srv-sb esmith::event[5167]: Action: /etc/e-smith/events/post-backup-data/S70cleanup-data-duplicity SUCCESS [0.057312] Nov 5 23:17:00 srv-sb esmith::event[5167]: Event: post-backup-data SUCCESS
Here is a clue. Using the old 980 interface it complained of
* Send notification to
empty
[Send notification to](https://domain:29980/en-US/BackupData#BackupData_notifyTo)
equal to root@localhost
[Send notification to](https://domain:29980/en-US/BackupData#BackupData_notifyTo)
invalid email address
In the cockpit interface we had 2 receiving email addresses. When I removed on in 980 interface the error warning has gone. Will watch to see it backup behaves tonight.