Forum Discussion

robtaylor's avatar
robtaylor
Level 2
8 years ago

Netbackup not writing to 1 of 2 drives

Hi Guys, Experiencing a very weird problem and looking for some assistance with troubleshooting this issue. Recently completed a hardware refresh and upgrade with current environment on Cisco C220 M...
8
ioctl
NetBackup 8.0
SCSI
Windows Server 2016
  • Mike_Gavrilov's avatar
    Mike_Gavrilov
    8 years ago

    1. What drive type do you have SAS or  FC?

    2. Have you tried to swap or replace FC/SAS cables?

    3. Could you share OS event logs because "The semaphore timeout period has expired" message comes from OS level and I belive it's just a result of timeouts.

    4. Have you tried L&TT(HP) or  ITDT(IBM) tools for tape drive diagnostic?

    You have 3 possible problem place:

    a) OS/driver

    b)TapeLibrary

    c)Physical connection

    I don't belive that NetBackup could be a reason of this message. Do you have a chance to connect the tape library to a linux host and run some tests? OS level tests without NetBackup with different OS\driver would help to exclude most possible reasons and show if connection or Tape Library itself is a root cause.

     

     

Mike_Gavrilov's avatar
Mike_Gavrilov
Level 6

1. What drive type do you have SAS or  FC?

2. Have you tried to swap or replace FC/SAS cables?

3. Could you share OS event logs because "The semaphore timeout period has expired" message comes from OS level and I belive it's just a result of timeouts.

4. Have you tried L&TT(HP) or  ITDT(IBM) tools for tape drive diagnostic?

You have 3 possible problem place:

a) OS/driver

b)TapeLibrary

c)Physical connection

I don't belive that NetBackup could be a reason of this message. Do you have a chance to connect the tape library to a linux host and run some tests? OS level tests without NetBackup with different OS\driver would help to exclude most possible reasons and show if connection or Tape Library itself is a root cause.

 

 

robtaylor's avatar
robtaylor
Level 2
7 years ago

Thanks guys, came back to update the solution to this issue. It turned out to be a driver issue. Even though the correct driver was used, the problem drive picked up an older driver and this was overlooked in initial troubleshooting.