View Issue Details

IDProjectCategoryView StatusLast Update
0000313bareos-coredirectorpublic2016-02-29 10:35
Reporterpstorz Assigned To 
PrioritylowSeverityfeatureReproducibilityhave not tried
Status acknowledgedResolutionopen 
Summary0000313: "rerun replay" command to replay jobs that would have been triggered in the past
DescriptionIn case of problems with the backup server, it is now already possible to rerun jobs that failed.

However, if the backupserver (director) was not running when the desired jobs would have been scheduled, we cannot rerun them as they never were scheduled.

I would suggest to have "rerun replay since=YYYY MM-DD HH:MM:SS" "days=-1" "hours=-1", and that would mean that we do trigger the jobs that would have been triggered since that point in time.

Avoiding duplicates will be important during this command.

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


There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2014-06-19 07:31 pstorz New Issue
2014-06-23 09:30 mvwieringen Severity minor => feature
2015-11-06 18:07 maik Priority normal => low
2015-11-06 18:07 maik Status new => acknowledged