Mandi! Martin Simmons
In chel di` si favelave...
> It is mentioned in the bullet point "Bacula currently does only minimal
> Storage conflict resolution" of the 9.4 manual page you listed above.
Bingo. The exact culprit came from the end of this bullet:
you always migrate to pools with different Media Types
So a migration need different media type; but currently there's no way to
specify different media type apart in Device{} resources on storage daemon,
so practicaly we need at least two device. And because:
Each Pool into which you migrate Jobs or Volumes must contain Volumes of only
one Media Type.
so we need also at least two pool.
> You definitely need two devices (one for reading, one for writing). It
> usually works if the media types are the same, but I've had one case of a
> deadlock in a Copy job.
In all my experimentation i was never able to have a working virtualfull job
with one device...
> If you have one media type, then you can define the two devices as a virtual
> autochanger like this in bacula-sd.conf:
Mmmhh... surely will work... but seems to me even more confusing then having
two devices...
Now work. Still many things are confusing to me, but i'll do more test and
provide
feedback back.
Thanks.
--
La virulenza delle polemiche su un argomento è inversamente
proporzionale alla reale importanza dell'argomento stesso.
(Legge di Potter)
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
