On Saturday 09 April 2005 16:36, Alan Brown wrote: > On Sat, 9 Apr 2005, Kern Sibbald wrote: > > Well, 1.36.x does use PoolId, but version 1.37.x uses StorageId, which > > ties it to the specific autochanger being used. > > Unless the StorageID is temporary and trashed each time update slots(*) is > run, this will be a really bad idea.
The StorageId is tied to the name of an autochanger, which may of course have multiple drives. > > Tapes need to be freely shiftable between drives _and_ autochangers, > especially in larger setups. The tape can only be in one autochanger at a time, thus the StorageId, which will be updated/refreshed when update slots is done. Moving a tape between autochangers is currently done with update slots, before long I will add it to update volume as well, so that you can manually move the tape. > > Drives need to be tied to autochangers so that a tape in one autochanger > isn't attempted to be loaded into a spare drive in another changer, but if > that tape is manually transferred then Bacula should just attach it to the > pool of available drives in the new autochanger This is *exactly* what my implementation does (well, to be more accurate, "is supposed to do" since no one has tested it yet), and I don't yet have a dual drive autochanger :-( Perhaps a gentle reminder from someone other than me would make it happen ... -- Best regards, Kern ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
