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
