In the log
The next release (R79) will add support for automatically retrying file system operations that fail for network-related reasons.
More specifically, the backup engine will retry an operation for up to
intervals when running into
Unexpected network error
Location is unreachable
and several other failures.
This should come especially handy when running larger backups over long connections, e.g. inter-branch VPNs or similar.
Prior to this release the engine already maintained a list of so-called
errors that causes a backup to be aborted if any of them is encountered.
These are errors like
IO device error
and they signal an unrecoverable condition that will cause all remaining backup steps to fail the same way.
Network-related failures were also on the list, but now they've been moved on a separate list of
errors, for which the engine is, basically, "trying harder".
The UI will still show a total error count in the job's summary, but it will render it in
if all errors were recovered from by retrying. See the
screengrab for details.
The retry count and the pause interval are configurable, but the
20 x 15 sec
default should work well in most cases.
It's also possible to add/remove error codes to both
lists, so if you ever need to retry on, say,
, you can certainly do that too.