View Issue Details

IDProjectCategoryView StatusLast Update
0000296bareos-core[All Projects] Generalpublic2021-06-26 23:14
ReporterMaxHeadroomAssigned To 
PrioritynormalSeverityfeatureReproducibilityN/A
Status acknowledgedResolutionopen 
Product Version 
Fixed in Version 
Summary0000296: Restart a backup after a error/pause but don't backup all files again.
DescriptionFor a full backup off an offsite it is neccassary to have these options:

*To restart a failed backup. The possiblity that there is an network break is really high because of a long backuptime.

*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.

regards Max
TagsNo tags attached.
bareos-master: impact
bareos-master: action
bareos-19.2: impact
bareos-19.2: action
bareos-18.2: impact
bareos-18.2: action
bareos-17.2: impact
bareos-17.2: action
bareos-16.2: impact
bareos-16.2: action
bareos-15.2: impact
bareos-15.2: action
bareos-14.2: impact
bareos-14.2: action
bareos-13.2: impact
bareos-13.2: action
bareos-12.4: impact
bareos-12.4: action

Activities

joergs

joergs

2014-05-16 17:21

developer   ~0000867

> *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.
MaxHeadroom

MaxHeadroom

2014-05-27 16:57

reporter   ~0000884

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.
TheChaosJack

TheChaosJack

2021-06-26 23:14

reporter   ~0004161

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.

Issue History

Date Modified Username Field Change
2014-05-13 17:12 MaxHeadroom New Issue
2014-05-16 17:21 joergs Note Added: 0000867
2014-05-16 17:21 joergs Status new => acknowledged
2014-05-27 16:57 MaxHeadroom Note Added: 0000884
2021-06-26 23:14 TheChaosJack Note Added: 0004161