It would be... ideal for me... if.... I could set for instance :
In the full source pool :
- Next Pool -> the monthly archive pool...
In the Job that performs the monthly archival :
- Next Pool -> the monthly archive pool...
In the Job that performs the annual archival :
- Next Pool -> the annual archive pool...
Could it be possible?.
The real reason of this question is that I'm writting the automation of
this configs... and... you know... it's a disaster for me creating the
same N schedules, but customized with the next pool for each of the
mensual and annual archival pools pair per catalogue we have... and as
said before... each pool, is named with the catalog name as seed of the
own pool name..... and that's why it would be far more comfortable for
me, to be able to enter the next pool in the job resource. I'm
suggesting to fix it in the own archival monthly and annual jobs in the
config file...
Can it be? :) :)
Thanks a lot mates :) :)
El 2022-05-25 18:47, egoitz--- via Bacula-users 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.
>
> Hi Josh,
>
> Could the NextPool=full_archive_pool1 be set in the own job definition?. It
> would be simplier for me... because the real pool names, use as a seed for
> the pool name the catalog in which they are....
>
> is that possible?.
>
> Best regards,
>
> El 2022-05-25 16:38, Josh Fisher 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/25/22 08:12, egoitz--- via Bacula-users wrote:
> Good morning,
>
> I have question for whom I have not find a possible answer in the net or my
> kindle Books of Bacula...
>
> I wanted to have two different pools with different retention periods for
> full copied jobs. In that pools I would like to do one of the following
> options :
>
> - To copy a full job from source full pool in a concrete moment of the year
> to full_archive_pool1
>
> - To copy a full job from source full pool in a concrete moment of the month
> to full_archive_pool2
>
> - To copy a full job from source full pool in a concrete moment of the year
> to full_archive_pool1 AND to copy a full job from source full pool in a
> concrete moment of the month to full_archive_pool2
>
> - Nothing
>
> I mean I would like that certain machines could have some "extra" full
> backups archived in that pools. Can be a monthly archived backup, an annual
> or both...
>
> My question is... if I define a schedule like for instance :
>
> Schedule {
> Name = ARCHIVAL_ANUAL_JANUARY_MONDAY_0000
> Run = Copy 1st mon on january at 00:00
> }
>
> Schedule {
> Name = ARCHIVAL_MENSUAL_MONDAY_0000
> Run = Copy 1st mon at 00:00
> }
> In the Run = line in each schedule, you may specify the
> NextPool=full_archive_pool1 for the yearly schedule and
> NextPool=full_archive_pool2 to the monthly schedule.
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.
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.
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
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._______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
