On 9/18/2014 6:37 AM, Roberts, Ben wrote: > Fair enough. > > I used a one-liner of bash to pre-create of my volume files and fill > the barcodes file, then used bconsole's label command to label all of > them in one go.
I agree that it isn't hard to pre-create volumes and put them in the Scratch pool. With pre-creating, volumes are moved from the Scratch pool to another pool when needed. With auto-labeling, volumes are created and labeled directly in the pool when needed. Either way, the net effect is pretty much the same. Anyway, as to the original question, if keeping the volumes for each client in a separate folder is a requirement, then it makes sense to have a separate device for each client. Otherwise, if the real requirement is to prevent volumes from containing jobs from more than one client, then a single device can still be used by having each client write to a different pool. ------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
