Hi Kjetil, I had a planned full backup which crashed. After this the next one was a incremental backup.... I think after a crashed planned full backup the next backup should be a full backup, not a incremental backup?
Regards
Stefan#
Am 27.09.2016 um 17:48 schrieb Kjetil Torgrim Homme:
> Stefan Klatt <stefan.kl...@cac-netzwerk.de> writes:
>> Am 26.09.2016 um 15:34 schrieb Daniel:
>>> Maybe this can help you.
>>> In my Jobs I use the following configuration:
>>>
>>> Max Full Interval = 1 Month ## maximales Alter des letzten
>>> Vollbackups. Ist keins vorhanden, wird ein neues geplant anstelle
>>> eines Inkrementellen Backups
>>> Max Diff Interval = 1 Week ## analog
>> that's a good idea. But what about the crashed full backup and after
>> this a incremental? This shouldn't happen :-(
> do you have an earlier Full backup with status OK ('T' or 'W') ? if so,
> Bareos will not think it is necessary to upgrade the job (unless you set
> the max interval mentioned by Daniel).
>
> there is also a setting for rerunning failed jobs. see the docs.
>
--
*CaC, Computer and Communication*
Inhaber Stefan Klatt
End-2-End Senior Network Consultant
Triftstrasse 9
60528 Frankfurt
Germany
USt-IdNr.: DE260461592
Tel.: +49-(0)172-6807809
Tel.: +49-(0)69-67808-900
Fax: +49-(0)69-67808-837
Email: stefan.kl...@cac-netzwerk.de
Profil: http://www.cac-netzwerk.de/profil
--
You received this message because you are subscribed to the Google Groups
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to bareos-users+unsubscr...@googlegroups.com.
To post to this group, send email to bareos-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: OpenPGP digital signature
