 |
> *To restart a failed backup. The possiblity that there is an network break is really high because of a long backuptime. it is possible, to restart a failed job with the "rerun" command, see http://doc.bareos.org > *Until the workhour it should be possible to pause the backup and resume after. > Maybe you can add an option that a fd is waiting for a reconnect and start after the last file that backup was ok. agreed, that this is a helpful feature. However, it will take quite some efford to implement it. We leave this ticket open as a reminder and feature request. |
|
|
as i understand is rerun = run again with the same options this would mean that in a case of network error all previous data has to backup again. For a initial offsite backup this could end up in a never ending accurate backup when the backup is running days. |
|
|
As I recently hit this issue while doing the initial backup of my NAS I found this issue. As Bacula supports exactly this since a few version (as far as I can tell also in the open source variant), maybe their code could make implementing this easier? Most likely even just trying to reconnect before declaring a backup as failed would help a lot, as most interruptions are either only short connection losses or misbehaving firewalls that drop the connection state for some reason leading to a broken connection. |
- Anonymous
