On 5/24/22 06:51, Heitor Faria wrote:
Still unsupported...
Sorry. You are right.
It is not needed for scalability purposes, but one Director can have many
different Catalogs as desired.
And each catalog will have its own unique Scratch pool. In fact, all of
the pools (and all other resources) defined in a particular catalog are
unique. Each customer could use the same pool names, because they are
using different catalogs. There is no overlap of pools, or of the
volumes contained in those pools.
What is impossible is a single, shared Scratch pool for all customers.
The Director can use more than one catalog, but a particular resource,
(Pool, Volume, Client, Job, etc.) can belong to only one catalog.
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
