Sorry, I am off on vacation now for several weeks. I am sure the list can help you.
A Bacula device does not hold Volumes rather it can "mount" (use) every Volume one at a time in the Archive Device directory you specify. The number is limited only by the number of files the filesystem permits a directory to hold. You can limit a device to a specific number of Jobs and to a specific MediaType. Best regards, Kern On 05/28/2013 09:09 PM, Dimitri Maziuk wrote: > On 05/28/2013 01:41 PM, Kern Sibbald wrote: >> I am wondering why and how you come up with ideas >> that don't correspond to what Bacula actually does. > Perhaps because all I know about what Bacula actually does is what I > read in the manual. (Don't get me wrong, it's no worse than the manuals > I write for my code -- that's why I'm on this ML & keep asking you.) > >> Every Device resource that is referenced by a virtual Autochanger >> resource in bacula-sd.conf is equivalent to a tape drive. The >> Volumes that have been created are equivalent to the slots, >> you get one slot per Volume -- as many as you want. > Please spell this out in simple words: I have 2 Devices in the > Autochanger, each Device can hold 5 Volume files. Bacula writes 5 > Volumes on Device-1, Device 1 is now full. What you're saying is bacula > will *not* write Volume-6 to Device-2, is that correct? (That's > certainly what's happening here.) > > What is the point of the virtual autochanger then? What is the intended > usage scenario? > ------------------------------------------------------------------------------ Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get 100% visibility into your production application - at no cost. Code-level diagnostics for performance bottlenecks with <2% overhead Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap1 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
