Re: [Bacula-users] Question about scratch pool
Still unsupported... -- MSc Heitor Faria (Miami/USA) CIO Bacula LatAm mobile1: + 1 909 655-8971 mobile2: + 55 61 98268-4220 [ http://bacula.lat/]___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Question about scratch pool
Hi! I don't use two directors. Just one director with different catalogues. I would never do that Heitor. Cheers, El 2022-05-23 18:36, Heitor Faria escribió: > ATENCION: Este correo se ha enviado desde fuera de la organización. No pinche > en los enlaces ni abra los adjuntos a no ser que reconozca el remitente y > sepa que el contenido es seguro. > > Egoitz, > > The Scratch pool is a hardcoded reserved name. > "Maybe" you will be luckier setting a "ScratchPool" for each one of the > Production pools. > Anyway: you are doing "gambiarra" (Brazilian Portuguese). > Bacula has its own means of providing multitenancy via ACLs, Pools, users etc. > Two Directors using the same catalog is not supported, according to Kern. > However, using (e.g.) a Pgsql cluster is supported for HA. > > Rgds. > -- > MSc Heitor Faria (Miami/USA) > CIO Bacula LatAm > mobile1: + 1 909 655-8971 > mobile2: + 55 61 98268-4220 > [ http://bacula.lat/]___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Question about scratch pool
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
Re: [Bacula-users] Question about scratch pool
Egoitz, The Scratch pool is a hardcoded reserved name. "Maybe" you will be luckier setting a "ScratchPool" for each one of the Production pools. Anyway: you are doing "gambiarra" (Brazilian Portuguese). Bacula has its own means of providing multitenancy via ACLs, Pools, users etc. Two Directors using the same catalog is not supported, according to Kern. However, using (e.g.) a Pgsql cluster is supported for HA. Rgds. -- MSc Heitor Faria (Miami/USA) CIO Bacula LatAm mobile1: + 1 909 655-8971 mobile2: + 55 61 98268-4220 [ http://bacula.lat/]___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Question about scratch pool
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. Now, when a catalogue goes out of appendable volumes that backup tasks stop awaiting for that new or appendable volumes. Someone (to which I'm very thankful for it's advises) with a big knowlegde about Bacula recommended, me to append tapes to Scratch pool and to use this pool as the recycle pool too. This way when new volumes are needed can be taken from the scratch pool. By the way, you can too recycle volumes to scratch pool, so that if a backup's total size dicreases that previously (but not now) needed tapes will end up in the scratch and you could always optimize the space for backups, because you know that tapes in the scratch can be removable. The problem here, is that we where thinking that the scratch pool, was a common pool in a director. So that any catalogue needing new volumes, could fetch them from there. By the way, if some other catalogues have excess of volumes, could become "thinner" because they could leave there those unneded volumes, so that another catalog who really is needing them, could then fetch. I was thinking in the scratch pool as a way of harmonize the server's catalogues disk usage (the usage of the volumes obviously). But I have had a bad surprise, when I have seen I couldn't do this, because Bacula, just uses tape knowledge inside the same catalog and the Scratch pool, even when being a special pool, it has the tapes registered in database and for each catalog. This is my real problem. In the doc, you didn't see in any place, that things are not as you think. It's trusth too, that you don't see the opposite too... Cheers, El 2022-05-23 17:29, Phil Stracchino escribió: > ATENCION > ATENCION > ATENCION!!! Este correo se ha enviado desde fuera de la organizacion. No > pinche en los enlaces ni abra los adjuntos a no ser que reconozca el > remitente y sepa que el contenido es seguro. > > On 5/23/22 10:39, egoitz--- via Bacula-users wrote: > >> Good morning, >> >> We are planning to use the Scratch pool for automatically having avaible >> tapes in the different pools of my different catalogues. >> >> For this purpose, we planned to create let's say 100 volumes in scratch and >> later, that volumes to to be requested by the different pooles AND of >> different catalogues, needing new media for continuating backup jobs. >> >> Is this possible or the scratch pool can only share volumes with pools >> within the same catalogue?. > > If you have multiple Catalogs, you would need to devise a way to synchronize > the state of the Scratch pool across all of them. This is not functionality > that is supported in Bacula. If you have multiple Bacula directors running > from different Catalogs, they need to be separate, not > sort-of-separate-but-with-overlaps. Trying to share resources between > Directors running from different Catalogs will get you into trouble, because > one director will have no way of knowing what another is using or has used. > This could lead to cases where, for example, one Director performs a critical > full backup on a certain set of tapes, and then the next day another Director > that doesn't know it has done so recycles one of those tapes and uses it for > something else, and the first doesn't know the backup is no longer valid. > > What are you trying to accomplish with this multiple-catalogs scheme? When > the answer doesn't make sense, sometimes it means you're asking the wrong > question.___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Question about scratch pool
On 5/23/22 10:39, egoitz--- via Bacula-users wrote: Good morning, We are planning to use the Scratch pool for automatically having avaible tapes in the different pools of my different catalogues. For this purpose, we planned to create let's say 100 volumes in scratch and later, that volumes to to be requested by the different pooles AND of different catalogues, needing new media for continuating backup jobs. Is this possible or the scratch pool can only share volumes with pools within the same catalogue?. If you have multiple Catalogs, you would need to devise a way to synchronize the state of the Scratch pool across all of them. This is not functionality that is supported in Bacula. If you have multiple Bacula directors running from different Catalogs, they need to be separate, not sort-of-separate-but-with-overlaps. Trying to share resources between Directors running from different Catalogs will get you into trouble, because one director will have no way of knowing what another is using or has used. This could lead to cases where, for example, one Director performs a critical full backup on a certain set of tapes, and then the next day another Director that doesn't know it has done so recycles one of those tapes and uses it for something else, and the first doesn't know the backup is no longer valid. What are you trying to accomplish with this multiple-catalogs scheme? When the answer doesn't make sense, sometimes it means you're asking the wrong question. -- 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
[Bacula-users] Question about scratch pool
Good morning, We are planning to use the Scratch pool for automatically having avaible tapes in the different pools of my different catalogues. For this purpose, we planned to create let's say 100 volumes in scratch and later, that volumes to to be requested by the different pooles AND of different catalogues, needing new media for continuating backup jobs. Is this possible or the scratch pool can only share volumes with pools within the same catalogue?. Best regards,___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
