I considered a similar approach at first, but after asking other users 
in this network, how long they want to keep backups, we decided on a 
rather long time period of multiple years. Considering that and the fact 
that we want to use one Volume per month, it would be a lot of work to 
pre-label everything.

So for now I switched back to simple devices without autochanger, so 
that the Volumes just get created when needed. I still have to test if 
it works though.

Regards,
Florian S.

Am 18.09.2014 um 11:42 schrieb Roberts, Ben:
> > Now I actually had to wonder: Is there no way to have bacula do both
> > labeling AND switching Volumes automatically?
> > Or do I just misunderstand?
>
> Personally I pre-label all my volumes into the Scratch pool, and let 
> Bacula handle moving volumes from there to a backup pool as needed. 
> They're then recycled back into the Scratch pool when the volume 
> retention period is reached. That way I can label up volumes just once 
> in a batch when purchasing new storage, and Bacula handles the rest. 
> Bacula doesn't need to re-label volumes during day-to-day operation.
>
> Regards,
> Ben Roberts


------------------------------------------------------------------------------
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 AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users