>On Sun, 15 Jan 2006 23:17:07 +0100, you wrote: >Hi, > >On 1/15/2006 10:46 PM, George R. Kasica wrote: >>>3. Upgrade to 1.38.4 (or whatever is current...). That version supports >>>multiple pools in one storage device. The upgrade is not exactly >>>hazardous, but to ensure a smooth start I'd recommend that, after you >>>upgrade the DIR, you issue a command like 'sqlquery >>>update Media set InChanger=0, Slot=0; >>> >>>update slots' >>>in bconsole to make sure you start with all the right catalog data. Note >>>that an upgrade requires a catalog update too, and an upgrade of all >>>clients and SDs in your installation. >>> >>>The quick solution for today, by the way, is to manually change the >>>catalog data to correctly represent the loaded volumes. Start with >>>setting InChanger and Slot for all volumesto 0, and then set the correct >>>values for the volumes currently loaded. Do this with your database >>>frontened, not through Baculas console. Don't use update slots afterwards. >>> >>>Hope this helps... and better make plans for an upgrading weekend. >>> >>>Arno >> >> Arno: >> >> I'm on 1.38.3 here, but the above raises a question: >> >> I have 2 pools of tapes for each autochanger here (obviously only one >> can be loaded at a time) what exactly does this feature allow? I'm not >> following here. Right now when I look at a List Volumes, it shows each >> pool of tapes in the correct slots and changers, even though only one >> group of 6 tapes is actually physically loaded into the device at any >> one time. >> >> Does that make any sense? > >Hmm. I'm not sure I completely understand your setup. Let me try to >express it in my words... > >You've got an autochanger device. For simplicity, we only talk about one >now, ok? Sure. Same question applies to all.
>You've got two pools of volumes for this autochanger, associated by a >media type setting, right? Yes, each goes into the 6 tape (or 7 tape depending on device) cartridge and then one of these is a pool say D0-SetA or D0-SetB for example. Both are obviously the same media type and go into the same device. >A 'list volumes' command shows you, for example, that in slot one of >your autochanger the volumes assigned to both pools are present. Which, >obviously, would be nonsense... True: >-----+------+-----------+-----------+---------------------+ >Pool: DDS-3-Drive0-Set-A >+---------+-----------------+-----------+----------+----------+--------------+---------+------+-----------+-----------+---------------------+ >| MediaId | VolumeName | VolStatus | VolBytes | VolFiles | VolRetention | >Recycle | Slot | InChanger | MediaType | LastWritten | >+---------+-----------------+-----------+----------+----------+--------------+---------+------+-----------+-----------+---------------------+ >| 11 | D0-SA-V1 | Append | 0 | 0 | 604,800 | > 1 | 1 | 0 | DDS-3 | 0000-00-00 00:00:00 | >| 12 | D0-SA-V2 | Append | 0 | 0 | 604,800 | > 1 | 2 | 0 | DDS-3 | 0000-00-00 00:00:00 | >| 13 | D0-SA-V3 | Append | 0 | 0 | 604,800 | > 1 | 3 | 1 | DDS-3 | 0000-00-00 00:00:00 | >| 14 | D0-SA-V4 | Append | 0 | 0 | 604,800 | > 1 | 4 | 1 | DDS-3 | 0000-00-00 00:00:00 | >| 15 | D0-SA-V5 | Append | 0 | 0 | 604,800 | > 1 | 5 | 1 | DDS-3 | 0000-00-00 00:00:00 | >| 16 | D0-SA-CLEAN0001 | Cleaning | 0 | 0 | 604,800 | > 1 | 6 | 1 | DDS-3 | 0000-00-00 00:00:00 | >+---------+-----------------+-----------+----------+----------+--------------+---------+------+-----------+-----------+---------------------+ >Pool: DDS-3-Drive0-Set-B >+---------+-----------------+-----------+----------------+----------+--------------+---------+------+-----------+-----------+---------------------+ >| MediaId | VolumeName | VolStatus | VolBytes | VolFiles | >VolRetention | Recycle | Slot | InChanger | MediaType | LastWritten | >+---------+-----------------+-----------+----------------+----------+--------------+---------+------+-----------+-----------+---------------------+ >| 17 | D0-SB-V1 | Full | 15,328,694,433 | 16 | >604,800 | 1 | 1 | 1 | DDS-3 | 2006-01-09 06:11:40 | >| 18 | D0-SB-V2 | Append | 486,943,359 | 1 | >604,800 | 1 | 2 | 1 | DDS-3 | 2006-01-09 06:23:42 | >| 19 | D0-SB-V3 | Append | 0 | 0 | >604,800 | 1 | 3 | 1 | DDS-3 | 0000-00-00 00:00:00 | >| 20 | D0-SB-V4 | Append | 0 | 0 | >604,800 | 1 | 4 | 1 | DDS-3 | 0000-00-00 00:00:00 | >| 21 | D0-SB-V5 | Append | 0 | 0 | >604,800 | 1 | 5 | 1 | DDS-3 | 0000-00-00 00:00:00 | >| 22 | D0-SB-CLEAN0001 | Cleaning | 0 | 0 | >604,800 | 1 | 6 | 1 | DDS-3 | 0000-00-00 00:00:00 | >+---------+-----------------+-----------+----------------+----------+--------------+---------+------+-----------+-----------+---------------------+ > >Is this a correct description? See above does that help any? >If it is, I'm unable to answer your question at the moment. >But, and this might be something worth a feature request (Kern, are you >reading this ;-) there should be a pre-defined query to print out which >volumes are loaded into which slots in which storage device. > >Well, anyway, concerning your situation, I'd really like to see either >output from 'list volumes' or the query I'll make available tomorrow. >And, of course, it would be interesting to know if you ever encounter >any problems. If there aren't any, what you describe would only be a >cosmetic problem, right? ;-) Output above. George ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
