Hello,
Each Device has a single directory associated with that device,
so in general, if you are writing volumes in different directories
you will need different MediaTypes. Though Pools are very useful,
there is really in most cases no requirement for them. For
Apologies, my terminology is off. I automatically prefix the files written
to backup with "job_name". These are written to sub-dirs of the storage
device (a mounted cifs) also named "job_name". This set of files in the
sub-dir is what I meant by backup set named "job_name".
With this scheme it is
Hello,
What you say sounds very strange. However, I cannot answer your
question:
"Trying to reuse a schedule definition causes backup sets to
be incorrectly named. Is that a correct deduction?"
is not possible because Bacula has no concept of naming a
Many thanks for those tips. I was almost there! I have it running nicely
now.
One thing that tripped me up was that the schedule definition requires the
volume pool used by the job be explicitly set. That seems to mean that each
job must have its own uniquely named schedule(s) defined - even
On 5/9/2018 5:37 PM, Chris Wilkinson wrote:
I am experimenting with using Bacula to back up several (m) cifs
shares on one Nas box to (n) sub-directories of a cifs share on
another. Neither Nas is able to run a client directly as they are
commercial locked down boxes.
My configuration is a
