ok, i'll try that, thanks
Samuel schrieb am Donnerstag, 30. November 2023 um 13:04:50 UTC+1:
> I think that's because the backup level is determined at the time the job
> is scheduled, so if the full has not yet finished by the time the job is
> scheduled again, it will again schedule another full backup.
> You can avoid this by configuring Allow Duplicate Jobs. See documentation
> here:
> https://docs.bareos.org/Configuration/Director.html#config-Dir_Job_AllowDuplicateJobs
>
> On Saturday, November 25, 2023 at 10:14:34 PM UTC+1 Markus Dubois wrote:
>
> I have started from scratch and did a full back.
> During the full job the scheduled job from the same source was launched in
> wait state as incremental.
>
> Everything fine so far….
> But then the full job ended successfully and afterwards the wait state job
> started.
>
> And it said in the logs ‚no prior full started full backup‘
>
> Why is that?
>
>
>
>
>
>
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/bareos-users/b3f2bd59-d31e-4626-8c72-4c60b6580d13n%40googlegroups.com.
