I have confirmed this behaviour:

The PoolUncopiedJobs select type for Copy jobs, determines that if the
second copy job will return not jobIDs to copy.

1) Backup job (Backup on main backup server's bacula SD), does a backup.
2) First copy job (Copy to 2nd backup server's bacula SD), does the copy of
the last backup with the PoolUncopiedJobs
3) Second copy job  (Copy to S3 with objectlock) will not found jobs to
copy as per the first copy job already copied the last backup.

Anyone had to deal with this situation? How can I run two differnet copy
job that copies the same jobid with the PoolUncopiedJobs ?


On Tue, Nov 29, 2022 at 4:19 PM Ivan Villalba <ivan.villa...@marfeel.com>

> Hi there,
> In order to follow the 3-2-1 backups strategy, I need to create a second
> copy type job to send backups to s3. The current client definition have two
> jobs, one for the main backup (bacula server), and a copy type job that,
> using the Next Pool directive in the original Pool, sends the backups to an
> external SD in a secondary bacula server.
> How do I create a second copy type job but using a third pool (not the
> original Next Pool), so I can send backups to S3?
> Thanks in advance.
> --
> Ivan Villalba
> SysOps - Marfeel

Ivan Villalba


[image: Inline images 4]
 [image: Inline images 3]

Avda. Josep Tarradellas 20-30, 4th Floor

08029 Barcelona, Spain

ES: (34) 93 178 59 50
US: (1) 917-341-2540 <%281%29%20917-341-2540%20ext.%20107>
Bacula-users mailing list

Reply via email to