Brian A. Seklecki wrote: > But in either configuration, the jobs launch at the same time in the > scheduler and run in series/serial. Thus, if the database is purged, > and each job is configured as incremental, and there is no record of a > full backup, each job is promoted to Full, so the first job runs > completes, then asks for the next tape in the pool.
Sounds like it marked the tape as 'Used' or 'Full' instead of leaving it open for appends... > This is not the expected behavior (imho). I'd expect it to consolidate > all jobs that are schedule to run at the same time, with the same > storage, same pool, same priority, to the same volume. Bacula will do this. Check you don't have "Maximum Volume Jobs = 1" in your configuration (although note that the configuration file settings only apply to newly created volumes - the value is set in the database for already created volumes, and needs updating explicitly if you want to change it. See the manual). Also, if you'd rather ensure that no single client is having multiple jobs run against it at once, then you could set maximum concurrent jobs to 1 for the client, I guess... -- Russell Howe [EMAIL PROTECTED] ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
