Hi all,
I'm having some struggles with automatic volume naming (utilizing job
id/name, client info and timstamp in the volume label) and concurrent
jobs in Bareos 17.2 using file backups and a single pool for all jobs.
The volumes are labeled to include information specific to the job.
Overall, it works pretty well. Unfortunately, when a job fails
(particularly when the file daemon isn't reachable), the next job
snatches up the volume.
For example, suppose I start the backup job for server1 (job ID 0001).
It will generate a volume like
0001-SysBak__server1.domain.com__2018-01-05-14.55.03. I then start some
other backups to run concurrently. Suppose there's a problem with that
first job (maybe the file daemon isn't responding) and it eventually
fails. The next queued backup (say for 0004 for server4) ends up
grabbing the volume for job 0001 and using it. The problem is, I don't
want backups for server4 stored in a volume that is labeled server1.
I'm generating my jobs out of a single pool, but I'm using multiple
devices (device definitions in the SD's config) to facilitate
concurrency which only allow one concurrent job each. This configuration
seems to work as long as none of the jobs fail.
Is there a way to ensure job XYZ for client ABC is the only job that
will be logged to volume XYZ-SysBak__ABC__ ?
Jason
--
You received this message because you are subscribed to the Google Groups
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/d/optout.
