On 2022-02-25 23:01, Bill Arlofski via Bacula-users wrote:
[...]
When customers start doing copy jobs and want to use the convenient
"PoolUncopiedJobs" feature, I usually recommend to start
by using a series of SQL queries instead.
The idea is to configure the Copy job to select jobs between two old
dates, then once that batch is done being copied, adjust
the SQL query to the next range of dates and continue this process
until the current date is reached. Then, the Copy job can
be changed to use the PoolUncopiedJobs feature and only the jobs that
have not been copied yet will be copied moving forward.
The other suggestion I make is, create a new pool and start sending
all of your backups there. Then, you can immediately
start using the PoolUncopiedJobs feature since only these new jobs
will need to be copied.
This second idea is OK, only if it is not necessary to copy all the
old jobs and you'd like to implement Copy jobs, starting
now...
And, for testing, just to make sure your Copy jobs are configured
correctly, you can make the Copy job select just one
specific jobid with the SQL query being simply: SELECT '1234' (where
1234 is the small backup job you want to test your Copy
job configuration with.
Several years ago I posted to this list an SQL query that copies only
the jobs that weren't already copied, while starting from the last
successful Full job. The post could still be found in the mailinglist
archives.
I used it when I had to start using Copy jobs but didn't want to
copy the whole pool as it was quite large.
--
Josip Deanovic
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
