On 12/9/2016 7:49 AM, Kern Sibbald wrote: > Sorry Josh, but Bacula never queries for available volumes (with the > exception of removable File media). The information in the Media record > is used to know which device should be used in many cases.
OK. What about tapes in autoloaders? I know it issues a LIST command to the mtx-changer script. I had assumed it was to identify the available tapes. Are you saying that if I have two SDs with identical autoloaders and using the same MediaType, I still cannot simply move tapes between the two autoloaders? > > On 12/09/2016 01:22 PM, Josh Fisher wrote: >> On 12/9/2016 6:32 AM, Martin Simmons wrote: >>> If a volume moves to a different location then it seems to me that changing >>> the StorageId is the logical thing to do. >> Has anyone tried simply moving them without changing the StorageId or >> anything else? Devices are directly queried for their available volumes. >> My guess is that volume location is decided from the queried >> information, not from the db. >> >> >>> IMHO, changing the Media Type of an existing volume is a timebomb waiting to >>> explode if you need to use bscan (because the existing label contains the >>> old >>> media type). >>> >>> __Martin >>> >>> >>>>>>>> On Fri, 9 Dec 2016 07:57:04 +0100, Kern Sibbald said: >>>> OK, I understand all those points, and >>>> I can say that Bacula will not notice by itself that Volumes have >>>> moved, so you will need to help it by using Pools or Media Types, >>>> but it should not require digging into StorageIds, which I don't >>>> think is even in the main manual. If it really *requires* >>>> changing the StorageId, then either I need to automate that or >>>> remove the dependency. >>>> >>>> Best regards, >>>> Kern >>> ------------------------------------------------------------------------------ >>> Developer Access Program for Intel Xeon Phi Processors >>> Access to Intel Xeon Phi processor-based developer platforms. >>> With one year of Intel Parallel Studio XE. >>> Training and support from Colfax. >>> Order your platform today.http://sdm.link/xeonphi >>> _______________________________________________ >>> Bacula-users mailing list >>> Bacula-users@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/bacula-users >> ------------------------------------------------------------------------------ >> Developer Access Program for Intel Xeon Phi Processors >> Access to Intel Xeon Phi processor-based developer platforms. >> With one year of Intel Parallel Studio XE. >> Training and support from Colfax. >> Order your platform today.http://sdm.link/xeonphi >> _______________________________________________ >> Bacula-users mailing list >> Bacula-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/bacula-users >> > > ------------------------------------------------------------------------------ > Developer Access Program for Intel Xeon Phi Processors > Access to Intel Xeon Phi processor-based developer platforms. > With one year of Intel Parallel Studio XE. > Training and support from Colfax. > Order your platform today.http://sdm.link/xeonphi > _______________________________________________ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users ------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today.http://sdm.link/xeonphi _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
