[Bacula-devel] RE: Migration

[David B. <db...@si...>]

=20
> The current scheme relies on the Storage definition in the=20
> Job resource. =20
> Until now, this has worked perfectly fine, but with=20
> Migration, the Storage device is no longer determined by the=20
> Job resource, but rather Pool to which the Migration has=20
> moved the data.

Hooray!

Yes, that is the likely case. This is actually good, though -- if you
take the view that the job should tell Bacula what to back up, and let
the storage management code worry about to what media and in what
sequence, then this is the logical consequence.=20

> As a consequence, it looks like Bacula is going to learn how=20
> to handle Storage definitions in Pool resources -- something=20
> you have always favored :-)

Great news. If it's any consolation, I think in the future this change
will also make the twinning mods easier.=20

It is consoling while thinking of you lounging away in sunny southern
France (it's 21 degrees F and raining here in Washington) ... *sigh*.


-- db