Hi mates!!
Nobody knows it then?. Could anyone know about my question of the Next
Pool directive?. Could it be set this way?.
_Job { _
_ Name = machine1-fd_copia_archivado_monthly_
_ JobDefs = machine1-fd_defs_
_ Type = Copy_
_ Level = Full_
_ Priority = 1_
_ NEXT POOL = MACHINE1_CATALOG_ARCHIVADO_MONTHLY_
_ schedule = one_invented_
_ Pool = machine1_catalog_archivado_monthly_
_ Storage = File-machine1c_
_ Selection Type = SQL Query_
_ Selection Pattern = "SELECT J\.JobId FROM Job J\, Pool P WHERE
P\.Name \= \'machine1_catalog_full\' AND J\.name like
\'\%$digitos_administrativo\%\' AND P\.PoolId = J\.PoolId AND
J\.level=\'F\' AND J\.Type = \'B\' AND J\.JobStatus IN \(\'T\'\,\'W\'\)
AND J\.jobBytes \> 0 AND J\.StartTime \> \(current_timestamp - interval
\'20 day\'\) ORDER BY J\.realendtime DESC LIMIT 1\"_
_}_
_Job { _
_ Name = machine1-fd_copia_archivado_yearly_
_ JobDefs = machine1-fd_defs_
_ Type = Copy_
_ Level = Full_
_ Priority = 1_
_ NEXT POOL = MACHINE1_CATALOG_ARCHIVADO_YEARLY_
_ schedule = one_invented_
_ Pool = machine1_catalog_archivado_yearly_
_ Storage = File-machine1c_
_ Selection Type = SQL Query_
_ Selection Pattern = "SELECT J\.JobId FROM Job J\, Pool P WHERE
P\.Name \= \'catalogo_$parte1_nombre_catalogo"."_full\' AND J\.name like
\'\%$digitos_administrativo\%\' AND P\.PoolId = J\.PoolId AND
J\.level=\'F\' AND J\.Type = \'B\' AND J\.JobStatus IN \(\'T\'\,\'W\'\)
AND J\.jobBytes \> 0 AND J\.StartTime \> \(current_timestamp - interval
\'20 day\'\) ORDER BY J\.realendtime DESC LIMIT 1\"_
_}_
Thank you so much mates. I'm writting some code for automating this
configurations and... I woud be extremely thankful if you could say me
that it's possible to set it that way, and end up with a Full job copy,
with the first job in the target pool machine1_catalog_archivado_monthly
and with the second job one, with the copy in the target
machine1_catalog_archivado_yearly...
I could end up by seeing it too... when testing all this... but if you
could save me some time, avoiding to write something is wrong and later
changing it... it would be really nice :) :)
Sorry if I'm asking so much :(
Very thankful, again for all your help,
Best regards,
El 2022-05-26 20:50, 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!!
>
> Perhaps I have not be very clear with my explanation sorry.... It happens my
> sometimes :) :) Sorry again :)
>
> I wanted to mean that... I preferred not to use in the Run line the "Next
> Pool" directive. For that purpose I have generated a couple of jobs :
>
> - One for monthly archival with it's schedule
>
> - One for yearly archival with it's schedule too...
>
> In that two jobs I have set the Next pool directive for avoiding the fact of
> using it in Run line in the schedule.
>
> So I planned something as :
>
> _Job { _
> _ Name = machine1-fd_copia_archivado_monthly_
> _ JobDefs = machine1-fd_defs_
> _ Type = Copy_
> _ Level = Full_
> _ Priority = 1_
> _ NEXT POOL = MACHINE1_CATALOG_ARCHIVADO_MONTHLY_
> _ schedule = one_invented_
> _ Pool = machine1_catalog_archivado_monthly_
> _ Storage = File-machine1c_
> _ Selection Type = SQL Query_
> _ Selection Pattern = "SELECT J\.JobId FROM Job J\, Pool P WHERE P\.Name
> \= \'machine1_catalog_full\' AND J\.name like \'\%$digitos_administrativo\%\'
> AND P\.PoolId = J\.PoolId AND J\.level=\'F\' AND J\.Type = \'B\' AND
> J\.JobStatus IN \(\'T\'\,\'W\'\) AND J\.jobBytes \> 0 AND J\.StartTime \>
> \(current_timestamp - interval \'20 day\'\) ORDER BY J\.realendtime DESC
> LIMIT 1\"_
> _}_
>
> _Job { _
> _ Name = machine1-fd_copia_archivado_yearly_
> _ JobDefs = machine1-fd_defs_
> _ Type = Copy_
> _ Level = Full_
> _ Priority = 1_
> _ NEXT POOL = MACHINE1_CATALOG_ARCHIVADO_YEARLY_
> _ schedule = one_invented_
> _ Pool = machine1_catalog_archivado_yearly_
> _ Storage = File-machine1c_
> _ Selection Type = SQL Query_
> _ Selection Pattern = "SELECT J\.JobId FROM Job J\, Pool P WHERE P\.Name
> \= \'catalogo_$parte1_nombre_catalogo"."_full\' AND J\.name like
> \'\%$digitos_administrativo\%\' AND P\.PoolId = J\.PoolId AND J\.level=\'F\'
> AND J\.Type = \'B\' AND J\.JobStatus IN \(\'T\'\,\'W\'\) AND J\.jobBytes \> 0
> AND J\.StartTime \> \(current_timestamp - interval \'20 day\'\) ORDER BY
> J\.realendtime DESC LIMIT 1\"_
> _}_
>
> The only reason is just a codding reason... for avoiding writting tons of
> Schedules one for each catalog... because as you see... the catalog is part
> of the name of the pool.... and... that was really the question.... if I
> could specify the next pool in the own archival jobs... creating one for each
> archival job....
>
> As always many thanks mates :)
>
> Cheers!!
>
> __________
>
> El 2022-05-26 14:33, Josh Fisher 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.
>
> On 5/25/22 12:47, egoitz--- via Bacula-users wrote:
>
> 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?.
>
> Yes. In the Run= line of the Schedule resource it is only needed to override
> the Job resource's NextPool setting. If you make NextPool=full_archive_pool1
> in the Job resource, then you will only need to add a
> NextPool=full_archive_pool2 override in the Run= line of the yearly schedule.
>
> 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.
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
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
