Quoting Kern Sibbald <[EMAIL PROTECTED]>:
You have multiple storage devices with the same Media Type pointing to the
same directory, which means that if you run concurrent jobs, you can have two
threads writing to the same file (Device:Volume), each with a different i/o
packet (Device) thinking it "owns" the volume. This will result in chaos and
corrupted backup Volumes. What you are doing is totally different from two
concurrent jobs writing to to the *same* Device, something that Bacula
handles quite well.
Hmmm... I'm having similar problem like Luke (see one of my recent
posts to the
list). Using bacula 1.36.3. Unlike Luke's configuration, my
configuration is a
simple one (basically, very few changes from the default configuration
files). I have only one storage device defined (media type = file), and
I have couple
of pools defined on it to have fulls and incrementals saved into different
files (again, using examples from documentation with little or no
changes). I'm doing concurrent backups, and director locks up from time
to time. The
only way to unlock it is to restart director. I can't even connect to it with
bconsole when it gets locked up. If I serialize backups (only single
backup at
a time), everything seems to work OK.
So, although Luke's configuration is probably broken, there seems to be a
problem with Bacula itself too when several jobs are written to the same file.
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc. Get Certified Today
Register for a JBoss Training Course. Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
