Kern Sibbald wrote: > On Wednesday 29 April 2009 11:58:15 James Harper wrote: > >>>> Kern, is it possible to have more than one Storage Daemon running on >>>> >> a >> >> >>>> machine ? >>>> >>> Yes, you can have as many as you want -- you just have to assign them >>> different ports. In general it is not necessary to have multiple >>> >> storage >> >> >>> daemons on a single machine because a storage daemon can handle >>> >> multiple >> >> >>> devices. >>> >> On that subject, I have just set up 1 'device' per client so that I can >> run the different clients in parallel while having one media file per >> client. It works really really well and makes a huge difference to the >> run time of the backup. The one annoying feature of that is that 'status >> storage' command now prompts me to select one of 10 different Storages, >> but in the end they all just give me the same information as they are >> all the same sd. >> > > What you are doing might be much easier using the disk-changer script with > multiple drives. As long as a Client has volumes in a unique Pool, each > client will have a different volume. > > You might even be able to do the same thing with a "pure virtual" > autochanger, > but I don't use that configuration much, and I think the documentation is > rather sketchy. The advantage of the pure virtual autochanger is that all > the Volumes would have the same name as seen in the catalog rather than > simply slot names. > >
I wrote a program called vchanger (now at http://sourceforge.net/projects/vchanger/) for doing this. Though written in C/C++, it is much like the disk-changer script, but allows loading any volume on any of its disk partitions into any of its virtual drives, the volume files are named the same as the barcode name, and it generates barcodes, rather than specifying them in a file. Autochangers are named and magazines numbered. The generated barcodes include the autochanger name, magazine number, and slot number, so it is easier (for me) to determine which drive a particular volume is on. Only a handful of people are currently using it, however. In any case, I find that the Scratch pool is tremendously helpful for this. By placing all of the autochanger's volumes initially in the Scratch pool, I can use as many different pools as needed without manually placing volumes into each pool. The number of virtual drives then more or less determines the max number of jobs that can run in parallel. >> Have you ever considered separating the 'Storage' and the 'Device' out >> in the director config? The configuration would then look something >> like: >> > > We do need some better concept of what a Storage is in the Director -- > currently it is not adequate, particularly concerning multiple autochangers > and MediaTypes and autochanger drive read/write characteristics so I am open > for suggestions. > I've always wondered if it would be possible to assign jobs to a MediaType only, rather than to a specific Storage device, so that the job could be assigned any available device in a pool of devices having that same MediaType. It's a tricky subject, since the next available volume in a pool might only be loadable on one particular device. Is this even possible? ------------------------------------------------------------------------------ Register Now & Save for Velocity, the Web Performance & Operations Conference from O'Reilly Media. Velocity features a full day of expert-led, hands-on workshops and two days of sessions from industry leaders in dedicated Performance & Operations tracks. Use code vel09scf and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
