On 5/23/22 12:05, egoitz--- via Bacula-users wrote:
Hi mates,
My purpose is the following one.
As I run backup of different customers :
- For better isolating them for managing permissions properly
- For separating quota usage
- For using more little databases
- And because it's done this way some time ago for several reasons (some
of them I can't really know now)
we are using different catalogues for our customers.
OK, so you are using one Director, but multiple Catalogs, one per customer?
As Heitor suggested, you could create a separate named ScratchPool in
each Catalog, but there is no way to *safely* share the same Scratch
pool across multiple catalogs, and I cannot begin to guess at what would
happen if the Director finds the same Pools in different Catalogs with
different volumes in them.
I would urge you in this case to try to make all resource names unique
to customers and NOT try to share anything between them. Trying to
share volumes in a common scratch pool would break the isolation you are
trying to create, and sounds like a cross-customer data breach mishap
waiting to happen.
--
Phil Stracchino
Babylon Communications
ph...@caerllewys.net
p...@co.ordinate.org
Landline: +1.603.293.8485
Mobile: +1.603.998.6958
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
