Bacula Users,
I'm using Bacula 5.0.0 with python scripting to create meaningful volume
labels that contain the client name for a disk based (Storage=File)
implementation.
The problem I'm seeing is that if a job fails to run due to a connection
error (there may be others), then the volume is left in append mode and my
next job, regardless of the client name uses that volume instead of creating
a new volume for itself.
For the pool definitions, I've got
Recycle = yes
AutoPrune = yes
Maximum Volume Jobs = 1
Use Volume Once = yes
Volume Retention = 2 months
The python script is basically the stock distributed one with this line for
the volume name in scripts/ DirStartUp.py
job.VolumeName="%s-%s-%0*d" % (client, pool, 4, numvol)
(it produces names like clientname-poolname-0001)
I've found very little on python scripting for bacula, but if anyone knows
how / where to intercept the error and mark the volume as "Used" instead of
"Append", I would be greatly appreciative.
I'm guessing it's not a version specific problem.
Thanks,
Jonesy
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
