Unsolved
1 Rookie
•
34 Posts
0
880
October 23rd, 2020 07:00
Backup server does not see tape library and drives
Hello,
Can you help me with this:
I am using Networker 19.1.1.1 version, the backup server cannot see the library any more, nothing at devices and library in NMC nd also in device manager at OS level (see attached photo)
the output of inquire -l:
********************************
PS C:\Users\wa_bh> inquire -l
-l flag found: searching all LUNs, which may take over 10 minutes per adapter
for some fibre channel adapters. Please be patient.
scsidev@0.0.0:hp DVD A DS8A5LH 1HE4|CD-ROM, \\.\CdRom0
scsidev@2.0.0:COMPAQ SCSI COMMUNICATECIS2|Unknown Device Type,
scsidev@2.4.0:HP LOGICAL VOLUME 5.14|Disk, \\.\PhysicalDrive0
S/N: 5001438017502AD0
WWNN=600508B1001CAC24F301F2E76276207C
VBNN=00000000
scsidev@2.5.0:HP LOGICAL VOLUME 5.14|Disk, \\.\PhysicalDrive1
S/N: 5001438017502AD0
WWNN=600508B1001CC49740E6850457D88D0B
VBNN=01000000
scsidev@10.0.0:COMPAQ SCSI COMMUNICATECIS2|Unknown Device Type,
2 Disk, 1 CD-ROM, 2 Unknown Device Type, Total: 5
******************************************
From hardware point of view, the library is connected to the server and there are no alerts!
It used to work properly then this issue occurs!
I rebooted the library, rescanned for HW changes.. but in vain..
Thank you for providing help.
bingo.1
2.4K Posts
0
October 24th, 2020 02:00
NW will only use what has been detected and reported by the OS. Consequently your problem is already the device detection on the OS level. Neither the autochanger nor a tape drive has been detected.
Can you connect the library to another PC and check whether it will be detected here?
hend_bs
1 Rookie
•
34 Posts
0
October 26th, 2020 07:00
Hello,
Thanks for the reply.
Yes we plugged the library to another server and we used another cable (because the other server requires a sas to mini sas cable) then the issue might be with the old cable (SAS to SAS) or at the server level ..
but actually we are migrating the networker service to that other server, That's why I stopped investigating about the root cause of the issue.