Forum Discussion

CAMILONOVOA's avatar
CAMILONOVOA
Level 3
14 years ago

DRIVE OFFLINE

HI
 
I followed step by step this article http://www.symantec.com/business/support/index?page=content&id=TECH24414&actp=search&viewlocale=en_US&searchid=1285176495535 and problem persists. My Powervault 124T LTO2 drive works perfectly and I checked using NTBACKUP. When you try to manage the unit SYMANTEC BackupExec 11D the unit is offline.
 
The last configuration I have done is change my LTO2 DRIVE PowerVault currently has a DRIVE QUANTUM CL1001 is the same reference
Originally the unit next PV124T (CL400 LTO2).
 
I need your help.
11.x and Earlier
Backup and Recovery
Backup Exec
Compatibility
Configuring
Installing
  • Larry_Fine's avatar
    Larry_Fine
    14 years ago

    I suggest disabling your tape library and drive in BE (right click | uncheck 'enable"), deleting your tape library and drive from the BE GUI, stop the BE services.  Make sure the tape library and drive are in the Windows device manager, then start BE services and let it detect your current hardware.

    If the device goes offline again, please check the adamm.log file for reasons.

18 Replies

Sort By
  • Larry_Fine's avatar
    Larry_Fine
    Level 6
    14 years ago

    I suggest disabling your tape library and drive in BE (right click | uncheck 'enable"), deleting your tape library and drive from the BE GUI, stop the BE services.  Make sure the tape library and drive are in the Windows device manager, then start BE services and let it detect your current hardware.

    If the device goes offline again, please check the adamm.log file for reasons.

  • CAMILONOVOA's avatar
    CAMILONOVOA
    Level 3
    14 years ago

     

    ok, I followed your instructions and appears in the adamm.log. After the restart, the drive appears off line.

     

     

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    [4296] 09/22/10 17:13:34.068 Adamm Log Started! ("SRVBTABCK01", 1000, {4D1BCEC1-243C-4774-838D-8FEAC9549415})
     
    Adamm Info: Version 11.0, Build 6235, 32bit
     
    OS Info: Windows NT 5.2, Build 3790, Service Pack 2
     
    Database Driver Info: SQLSRV32.DLL, 03.86.3959
    Database Server Info: Server Name = "SRVBTABCK01", Active Node = ""
    Database Connection String: "DRIVER=SQL Server;SERVER=srvbtabck01\BkupExec;DATABASE=BEDB;App=BEWS PVL"
     
    DateTimeSync: Local = 2010/09/22 17:13:34, System = 2010/09/22 22:13:34 GMT, Database = 2010/09/22 22:13:34 GMT
     
    Shared Storage Authorization: No
    TSM Authorization: Yes
    Library Expansion Options: 1
     
    [6120] 09/22/10 17:13:34.114 Read Device Records - start 
     
    [6120] 09/22/10 17:13:34.177 Read Device Records - end
     
    [6120] 09/22/10 17:13:34.317 iSCSI Discovery - start 
     
    The iSCSI initiator software does not appear to be installed on this system
     
    [6120] 09/22/10 17:13:34.317 iSCSI Discovery - end 
     
    [6120] 09/22/10 17:13:34.505 Read NDMP Server Records - start 
     
    [6120] 09/22/10 17:13:34.551 Read NDMP Server Records - end
     
    [6120] 09/22/10 17:13:34.551 DeviceIo Discovery - start
     
    [6120] 09/22/10 17:13:34.551 DeviceIo Discovery - end
     
    [6120] 09/22/10 17:13:34.551 DeviceIo Devices:
     
    Scsi Address
    Prt :Bus :Tar :Lun   Attributes
    -------------------  -------------------------------------------------------------------------------
     
     
    -------------------  -------------------------------------------------------------------------------
     
    [6120] 09/22/10 17:13:34.551 Device Registry:
     
    Scsi Address
    Prt :Bus :Tar :Lun   Attributes
    -------------------  -------------------------------------------------------------------------------
     
    0000:0000:0000:0000  "atapi", (Port Driver)
     
    -------------------  -------------------------------------------------------------------------------
     
    0001:0000:0000:0000  "atapi", (Port Driver)
     
    -------------------  -------------------------------------------------------------------------------
     
    0002:0000:0000:0000  "mraid35x", (Port Driver)
     
    -------------------  -------------------------------------------------------------------------------
     
    0003:0000:0000:0000  "adpu160m", (Port Driver)
     
    -------------------  -------------------------------------------------------------------------------
     
    0004:0000:0000:0000  "adpu160m", (Port Driver)
    0004:0000:0006:0000  "CERTANCEULTRIUM 2       1914", (Tape Device), "\\.\Tape0"
    0004:0000:0006:0001  "DELL    PV-124T         0080", (Changer Device), "\\.\MediumChanger0"
     
    -------------------  -------------------------------------------------------------------------------
     
    [6120] 09/22/10 17:13:34.551 PnP Device Paths:
     
    Scsi Address
    Prt     :Bus     :Tar     :Lun       Device Path
    -----------------------------------  ---------------------------------------------------------------
     
    00000004:00000000:00000006:00000000  \\?\scsi#sequential&ven_certance&prod_ultrium_2&rev_1914#6&73f2152&1&060#{53f5630b-b6bf-11d0-94f2-00a0c91efb8b}
     
    -----------------------------------  ---------------------------------------------------------------
     
    [6120] 09/22/10 17:13:34.551 Read Device Inquiries - start
     
    [6120] 09/22/10 17:13:34.567 Device: \\.\Tape0
    [6120] 09/22/10 17:13:34.957 Device: \\.\MediumChanger0
     
    [6120] 09/22/10 17:13:35.285 Read Device Inquiries - end
     
    [6120] 09/22/10 17:13:35.285 Serialize Devices:
     
    [6120] 09/22/10 17:13:35.878 Device Discovery:
     
    Scsi Address
    Prt :Bus :Tar :Lun   Attributes
    -------------------  -------------------------------------------------------------------------------
     
    0004:0000:0006:0000  Device Name             "\\.\Tape0"
                         Secondary Name          "\\?\scsi#sequential&ven_certance&prod_ultrium_2&rev_1914#6&73f2152&1&060#{53f5630b-b6bf-11d0-94f2-00a0c91efb8b}"
                         Primary Inquiry         "CERTANCEULTRIUM 2       1914"
                         Serial Number           "CERTANCEULTRIUM 2        JK10Z9Q"
                         Device Flags            KSCSI, SN(TYPE 1)
                         Device State            3, Online
     
                         Device IDs              1011, {1B8A754F-F3A9-4894-B933-9BD0BD0DE7A5}
                         Device Name             "CERTANCE 1"
                         Device Type             134283265, "LTO 64K (64K,10,0,E,HU)"
                         Device Features         0x000BFA7F: PB,SFB,SRB,WFM,SFF,SRM,PEOD,EL,LU,E,SBS,DC,SDC,TA,HU,RR
                         Device Element          0, 0
     
    0004:0000:0006:0001  Device Name             "\\.\MediumChanger0"
                         Secondary Name          "\\.\Changer0"
                         Primary Inquiry         "DELL    PV-124T         0080"
                         Secondary Inquiry       "DELL    PV-124T         0080"
                         Serial Number           "DELL    PV-124T         CH6FC21306"
                         Device Flags            KSCSI, SN(TYPE 1)
                         Device State            3, Online
     
                         Device IDs              1002, {9C4D621A-3AF1-4A62-A2D0-63DCC9BF6DE1}
                         Device Name             "PowerVault 124T"
                         Device Type             2131755008, "CHANGER FS=1"
                         Device Features         0x0035784A: EMBM,INSMC,MSTS,PT,PMA,RMP,RRD,SMCAE,TEI,IIE,IMSMC
                         1st Slot Number         1
                         Number Of Slots         16
                         Portal Slots            0
                         Import/Export           Manual
     
                         Drive Element 0         1003, ""
     
    -------------------  -------------------------------------------------------------------------------
     
    [6120] 09/22/10 17:13:36.018 Start Rsm Support:
     
    [6120] 09/22/10 17:13:36.034 Device Discovery End:
  • pkh's avatar
    pkh
    Moderator
    14 years ago

    Go to the BE installation directory and start up tapeinst.exe.  Delete all reference to your old tape drive and then add your new tape drive.  After that, power off both your media server and tape library.  Start up your tape library and then your media server.  Your new tape drive should be online.

  • Mahesh_Roja's avatar
    Mahesh_Roja
    Level 6
    14 years ago

    in your log

    The iSCSI initiator software does not appear to be installed on this system

    Just check the driver for that tape in your backup exec.

  • CraigV's avatar
    CraigV
    Moderator
    14 years ago

    If it worked with NTbackup, but not BE 11d...have you checked to make sure your Removable Storage service is stopped and disabled? This causes known issues with the way that BE manages the hardware.

     

    @Maheshroja - the poster mentioned NOTHING about an iSCSI device...it is a SCSI tape library, connected via a SCSI card and cable...

  • CAMILONOVOA's avatar
    CAMILONOVOA
    Level 3
    14 years ago

     

    Hi 
     
    I've completed the instructions and the problem exists. I think the problem is:
     
    1. PowerVault124T original comes with a Certance CL400 LTO2 drive. As damage this unit was replaced by a new reference is QUANTUM CL1001 LTO2.
     
    2. Certance CL400 is the same as QUANTUM CL1001.
     
    Now in the document Backup Exec 11d (11.0) for Windows Servers Hardware Compatibility Lists (http://www.symantec.com/business/support/resources/sites/BUSINESS/content/staging/TECHNICAL_SOLUTION/46000/TECH46703/en_US/ 3.0/282249.pdf? __gda__ = 1285255984_bd4c618a91c84bfdeaff450b8e258ed1) in the section "tape Libraries with Drives" that the PowerVault124T only recognize Certance CL 400, there is no alternative, affecting the Inquiry string matches
     
    There will be a hotfix or update that help me the problem ????

     

  • Larry_Fine's avatar
    Larry_Fine
    Level 6
    14 years ago

    Is that the complete adamm.log?  According to the adamm.log, your library and drive are ONLINE.

    Device State            3, Online

    Was there anything more (maybe it takes soome time) after the "device discovery end"?

  • Larry_Fine's avatar
    Larry_Fine
    Level 6
    14 years ago

    Do the CL400 and the CL1001 have the same CERTANCEULTRIUM^2 inquiry string?  If they do, then they both should work as I suspect they just updated the marketing name as the product evolved.  According to the adamm.log posted above, the library and drive are discovered correctly and are online.

    To answer your other question, no, I doubt any driver updates would ever be issued for such an old version of Backup Exec, but ti doesn't appear that you need any driver patches anyway.

  • CAMILONOVOA's avatar
    CAMILONOVOA
    Level 3
    14 years ago

     

    it means when in the adamm.log  it refers to:
     
    [6120] 09/22/10 17:13:34.317 iSCSI Discovery - start
     
    The iSCSI initiator software does Not Appear to be installed on this system
     
    [6120] 09/22/10 17:13:34.317 iSCSI Discovery - end