Re: [Bacula-users] Progressive Virtual Fulls...

[Radosław K. <rad...@ko...>]

Hello,

pt., 22 wrz 2023 o 12:41 Marco Gaiarin <ga...@li...> napisał(a):

> > Device  {
> >         Name = tethysFileStorage
> >         Media Type = tethysFile
> [...]
> > Device  {
> >         Name = tethysVirtualFileStorage
> >         Media Type = tethysVirtualFile
>
> Ah. You defined TWO device, with different media type; i've not found
> anywhere notes about the need of different devices/mediatype; seems also a
> single pool can be used...
>

You always need two devices for this, it is described in the docs. You do
not need different media types if you carefully manage pool configuration.


> But another point in the documentation ring me a bell:
>
>  Jobs on Volumes will be considered for Migration only if the Volume is
> marked, Full, Used, or Error. Volumes that are still marked Append will not
> be considered for migration. This prevents Bacula from attempting to read
> the Volume at the same time it is writing it. It also reduces other
> deadlock situations, as well as avoids the problem that you migrate a
> Volume and later find new files appended to that Volume.


Exactly.


> So i've tried to put on 'Used' the volume that contain the full and the
> incremental; this sounds strange to me (because if i run a job, even on an
> Append volume, they read on jobids to consolidate...) but...
>
> Anyway, nothing changed. I've run the VirtualFull but job is stalled.
>

Share your job logs for this.

R.
-- 
Radosław Korzeniewski
rad...@ko...