Hello,
usually I do not have problem with concurrent jobs, because they
read/write from/to different pools. But when it comes to virtual full
backups I need to stop bacula from doing these jobs concurrently.
Is there a way to tell the bacula to do a certain type of job one at a
time even if the configured standard is to accept 12 jobs concurrently?
How is that done with copy/migration jobs e.g. The doc says there is a
management job which starts the actual copy/migration job. These run
one at a time just fine in my environment. How can I impelement this
behaviour for my virtual full jobs?
Any hints?
Cheers Jan
--
MAX-PLANCK-INSTITUT fuer Radioastronomie
Jan Behrend - Rechenzentrum
----------------------------------------
Auf dem Huegel 69, D-53121 Bonn
Tel: +49 (228) 525 359, Fax: +49 (228) 525 229
jbehrend AT mpifr-bonn.mpg DOT de http://www.mpifr-bonn.mpg.de
smime.p7s
Description: S/MIME cryptographic signature
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
| 