I'm new to the configuration of Networker and I have few problems to get the tape drives recognised by my Linux boxes.
My backup server is a windows box while I have 4 Red Hat Linux boxes (kernel 2.6.9-22.0.2.ELsmp) that should be configured as Storage Node as they are directly connected to the tape library via fibre channel. My tape library is a HP MSL5026 with 2 tape heads.
The zoning on my fibre channel switches is correctly configured because I can see the jukebox but I cannot see the 2 tape drives (it's my understanding that I should see them as 2 separate devices).
Here is the output of the Networker inquire command :
The NS E1200-160 (scsi0 Channel: 00 Id: 02 Lun: 02) seems to have something to do with the library because it's mentioned in the fibre channel switch and the backup server but not sure what exactly it is.
Am I right thinking that I should see the two tape drives as separate devices?
Any help on this is greatly appreciated as I've lost a lot of time on this without finding an explanation/solution.
From NetWorker point of view, you have better chances of having less problem with your backup after with kernel 2.4.x than 2.6.x (at least with 7.1.x and 7.2.x). So I would change that first. This probably is not related to your problem, but while you are still configuring this...
Second, you will need to set stinit, meaning your st driver should be loaded first and then stinit.def should be configured.
According to output you sent you don't see those drives at all. Once you see them you should see them as nst devices.
As you wish, but even with 7.3 kernel 2.4.XX is supported one - check installation guide page 20. 2.6.x is still not officially supported and I know some people had problems before (unrelated to NetWorker but rather st stuff) - not sure how things stand with current version of kernel.
Then you don't need to worry about platform. As for kernel, check that with support or presales. Primary now is to get devices being visible to Linux system itself. Once this is done you won't have problems configuring those.
I believe you can communicate with library if you run something like sjirdtag 0.2.0 (0.2.0 was SCSI address of your library accroding to your first post). See if you can commnicate by sending query to the library with this command. If not, then you have two problems - library communication and drive presence.
you are right, you should see 2 entries for the tapes. I don't see any tapes in the output you provided. Have a look at the output of the command 'dmesg' or look in /var/log/messages . You shoul find something like the output below (e.g.: Qlogic Controller). ... scsi2 : qla2300 Vendor: EXABYTE Model: Exabyte 110L Rev: 3.6 Type: Medium Changer ANSI SCSI revision: 02 Vendor: IBM Model: ULTRIUM-TD1 Rev: 36U3 Type: Sequential-Access ANSI SCSI revision: 02 ...
This would tell you that the fibre channel controller did recognise the tape (Sequential-Access). If you don't see any Sequential-Access then probably you zoning is wrong or your FC router is not setup correctly.
Maybe you can provide some more details about you HW My example above is an Exabyte 110L with one LTO drive. What tape drives models are you using e.g.: lto ? Are the tapes native fibre channel or connect via the router ?
You will need 7.3 for amd64. Available packages are: - Linux (IA-64 64 bit) Client, Server and Storage Node package - Linux (x86 & IA-32 32-bit) Client, Server and Storage Node package - Linux (x86, amd64 & em64T 64-bit) Client, Server and Storage Node package
According to compatibility list they are listing only 2.4 kernel, but I heard that 7.3 should have brought support for 2.6 kernel as well. Best thing would be to check this with support or even presales as they can get to this information.
Thanks for the information, I had overlooked this.
my HW is AMD64 but in the documentation I found only i386 and Itanium. Do you know where I can check if AMD64/Red Hat 2.6 is supported? I suppose it isn't if the more common i386 is not.
I checked the output of dmesg and I see nothing about the tape drives, I've got entries for the library though.
I run sjirdtag 0.2.0 and the result is : 0.2.0: No such device
... but, I have no stinit.def defined. I've downloaded an example from the legato website but I suppose I need to specify what library / tapes I've got? I'm looking for an example for the SDLT320... I bet you have got one ?! :))
ble1
6 Operator
•
14354 Posts
•
56186 Points
415
0
Posted February 10th, 2006 04:00
Second, you will need to set stinit, meaning your st driver should be loaded first and then stinit.def should be configured.
According to output you sent you don't see those drives at all. Once you see them you should see them as nst devices.