Il 27/03/2017 01:19, Tomasz Michno ha scritto: > [root@BRZE-BareOS bareos-sd.d]# mtx -f > /dev/tape/by-id/scsi-1IBM_3573-TL_00L2U78BW629_LL0 status > Storage Changer /dev/tape/by-id/scsi-1IBM_3573-TL_00L2U78BW629_LL0:1 > Drives, 24 Slots ( 1 Import/Export ) > Data Transfer Element 0:Full (Storage Element 1 Loaded):VolumeTag = BB0044L5 > Storage Element 1:Empty > Storage Element 2:Full :VolumeTag=BB0043L5 > Storage Element 3:Full :VolumeTag=BB0042L5 > Storage Element 4:Full :VolumeTag=BB0041L5 > Storage Element 5:Full :VolumeTag=BB0027L5 > Storage Element 6:Full :VolumeTag=BB0026L5 > Storage Element 7:Full :VolumeTag=BB0028L5 > Storage Element 8:Full :VolumeTag=BB0037L5 > Storage Element 9:Full :VolumeTag=BB0036L5 > Storage Element 10:Full :VolumeTag=BB0030L5 > Storage Element 11:Full :VolumeTag=BB0029L5 > Storage Element 12:Full :VolumeTag=BB0032L5 > Storage Element 13:Full :VolumeTag=BB0040L5 > Storage Element 14:Full :VolumeTag=BB0039L5 > Storage Element 15:Full :VolumeTag=BB0038L5 > Storage Element 16:Full :VolumeTag=BB0031L5 > Storage Element 17:Full :VolumeTag=BB0033L5 > Storage Element 18:Full :VolumeTag=BB0034L5 > Storage Element 19:Full :VolumeTag=BB0035L5 > Storage Element 20:Full :VolumeTag=BB0024L5 > Storage Element 21:Full :VolumeTag=BB0025L5 > Storage Element 22:Full :VolumeTag=CLNU58L1 > Storage Element 23:Full :VolumeTag=BB0045L5 > Storage Element 24 IMPORT/EXPORT:Empty
So your hardware infrastructure can _CORRECTLY_ recognize the physical tapes inside your T/L. This is good, as it's an (obvious) requirements for BareOS to properly work. Let's step over. You're going, now, to ask BareOS, via the "status slot" command issued in "bconsole", what BareOS knows about such tapes: > *status slots storage=Tape The good news is that BareOS _recognize_ there are physical tapes: > Connecting to Storage daemon File at BRZE-BareOS:9103 ... > 3306 Issuing autochanger "slots" command. > Device "3573-TL" has 24 slots. > Connecting to Storage daemon File at BRZE-BareOS:9103 ... > 3306 Issuing autochanger "listall" command. > Slot | Volume Name | Status | Media Type | Pool > | > ------+------------------+-----------+----------------+--------------------------| > 1*| BB0044L5 | ? | ? | > ? | > 2*| BB0043L5 | ? | ? | > ? | > 3*| BB0042L5 | ? | ? | > ? | > 4*| BB0041L5 | ? | ? | > ? | > 5*| BB0027L5 | ? | ? | > ? | > 6*| BB0026L5 | ? | ? | > ? | > 7*| BB0028L5 | ? | ? | > ? | > 8*| BB0037L5 | ? | ? | > ? | > 9*| BB0036L5 | ? | ? | > ? | > 10*| BB0030L5 | ? | ? | > ? | > 11*| BB0029L5 | ? | ? | > ? | > 12*| BB0032L5 | ? | ? | > ? | > 13*| BB0040L5 | ? | ? | > ? | > 14*| BB0039L5 | ? | ? | > ? | > 15*| BB0038L5 | ? | ? | > ? | > 16*| BB0031L5 | ? | ? | > ? | > 17*| BB0033L5 | ? | ? | > ? | > 18*| BB0034L5 | ? | ? | > ? | > 19*| BB0035L5 | ? | ? | > ? | > 20*| BB0024L5 | ? | ? | > ? | > 21*| BB0025L5 | ? | ? | > ? | > 22*| CLNU58L1 | ? | ? | > ? | > 23*| BB0045L5 | ? | ? | > ? | > 24@| ? | ? | ? | > ? | ...but... the bad news is that BareOS knows _NOTHING_ about those tapes, with the only exception of the "external label" passed him from the barcode reader (more or less). That's why, in the output above, you see a question mark in the "Status", "media Type" and "Pool" columns. If you think carefully to this.... you see that it's _correct_. At this point, BareOS still _DON'T_ have any information about those tapes inside his own catalog (aka: the DB used by the Director to handle all of his activities). This is shown, in the output above, by the "*" character shown right after the Slot id. And... this is the very reason why here: http://doc.bareos.org/master/html/bareos-manual-main-reference.html#x1-25500019.13 you can read: 19.13 Use bconsole to display Autochanger content <http://doc.bareos.org/master/html/bareos-manual-main-reference.html#QQ2-1-484> [...] If you see a * near the slot number, you have to run update slots command to synchronize autochanger content with your catalog. HTH :-) Bye, DV P.S.: Let me take this opportunity to point you this FUNDAMENTAL concept: BareOS is _REALLY_ powerfull. Much... much more than a common user might guess. But the barriers that need to be "jumped" to start using it in an effective manner, are _VERY_HIGH_. That' why here: http://doc.bareos.org/master/html/bareos-manual-main-reference.html#x1-50001.2 is clearly reported: "/if you are new to Unix systems or do not have offsetting experience with a sophisticated backup package, the Bareos project does not recommend using Bareos as it is much more difficult to setup and use than tar or dump/". So, please, if you really need (and want) all of the feature of a sophisticated backup infrastructure that BareOS can provide... be ready to "read", to "study", to "experiment" and... to "struggle" (...and to report here about your progress) :-) P.P.S.: your way to "document" your POSTs, on this list, is really detailed. Thanks for this :-) -- Damiano Verzulli e-mail: [email protected] --- possible?ok:while(!possible){open_mindedness++} --- "...I want to serve my diskless Beowulf nodes via iSCSI with LVM over RAID5 on IDE disks ..." Oliver Xymoron (mlist.linux.scsi) -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
