Hello Justin,
It seems that the Copy Pool directive has not been fully implemented. It
was added in 2007 but nothing else happened with it.
Here you can read feature request for the Copy Pool:
https://gitlab.bacula.org/bacula-community-edition/bacula-community/-/commit/fe27bfb5190d54a23b06368390
Hi there,
today I switched to using copy jobs to create the tier 2 backup (instead of
backup jobs from the original source). I realized that the copied job on tier 2
storage has the exact same name as the job on tier from which it was copied.
I am now unclear how I can schedule verify jobs for
Hi there,
I took this snipped from the main documentation about copy jobs:
# # Fake client for copy jobs #
Client {
Name = None
Address = localhost
Password = "NoNe”
Catalog = MyCatalog
}
# # Default template for a CopyDiskToTape Job # JobDefs {
Name = CopyDiskToTape
Type = Copy
Me
Hi there,
while in the process of trying out copy jobs I realized that Baculum has two
directives for pools:
Next Pool: according to the documentation this is used for migration jobs and
for copy jobs
Copy Pool: not found in the documentation. I can only guess that this suggests
that Copy Poo
