New hardware not recognized - Veritas Backup Exec

This is a discussion on New hardware not recognized - Veritas Backup Exec ; Version 9.0.4202 for Netware I added an Exabyte VXA-320 drive. The server sees the drive and BEDIAG sees it as well. However, scan for new devices doesn't find the new drive. I installed the latest drivers in the BKUPEXEC\NLMS folder ...

+ Reply to Thread
Results 1 to 5 of 5

Thread: New hardware not recognized

  1. New hardware not recognized


    Version 9.0.4202 for Netware
    I added an Exabyte VXA-320 drive. The server sees the drive and BEDIAG sees
    it as well. However, scan for new devices doesn't find the new drive. I installed
    the latest drivers in the BKUPEXEC\NLMS folder and restarted.

    I found a TID for 8.5 that says you have to delete the hardware database
    and restart BE for new hardware to be found. However, BKUPEXEC\PM does not
    exist. I do have BKUPEXEC\MM. Are they the same thing?

    Any suggestions?

  2. Re: New hardware not recognized

    Post the output from LIST STORAGE ADAPTERS.

    -Barry.


  3. Re: New hardware not recognized

    Ken Berg wrote:

    >
    > Version 9.0.4202 for Netware
    > I added an Exabyte VXA-320 drive. The server sees the drive and
    > BEDIAG sees it as well. However, scan for new devices doesn't find
    > the new drive. I installed the latest drivers in the BKUPEXEC\NLMS
    > folder and restarted.
    >
    > I found a TID for 8.5 that says you have to delete the hardware
    > database and restart BE for new hardware to be found. However,
    > BKUPEXEC\PM does not exist. I do have BKUPEXEC\MM. Are they the same
    > thing?


    Yes. Try the following to see if this helps:

    1. BESTOP
    2. Rename :\bkupexec\mm to mm.old
    3. BESTART

    If that doesn't help, as Barry said, please post back with the results
    of typing LIST STORAGE ADAPTERS at the server console.

    Chris


  4. Re: New hardware not recognized


    Renaming the MM directory didn't work. Here's the results of list storage
    adapters:

    IWHC_01:list storage adapters
    0x00 [V651-A0] PERC2 Host Aadapter Module [slot 10005]
    0x08 [V651-A0-D6:0] Unbound Device Object
    0x01 [V651-A1] PERC2 Host Adapter Module [slot 10005]
    0x07 [V651-A1-D1:0] DELL RAID Device 0:01 rev:1.0
    0x06 [V651-A1-D0:0] DELL RAID Device 0:00 rev:1.0
    0x02 [V651-A2] PERC2 Host Adapter Module [slot 10005]
    0x03 [V651-A3] PERC2 Host Adapter Module [slot 10005]
    0x04 [V651-A4] PERC2 Host Adapter Module [slot 10005]
    0x05 [V651-A5] PERC2 Host Adapter Module [slot 10005]
    0x09 [V321-A6] Adaptec AIC-7899 - Ultra160 SCSI [slot 10003]
    0x0A [V312-A7] Adaptec SCSI Adapter [slot 10004]
    0x0C [V312-A7-D6:0] BNCHMARKDLT1 391B
    0x0B [V312-A7-D5:0] NEC CD-ROM DRIVE:466 rev:1.06
    0x13 [V321-A8] Adaptec SCSI Card 29160 - Ultra160 SCSI [slot 1]
    0x14 [V321-A8-D2:0] EXABYTE VXA-3 310E

    The BNCHMARKDLT1 is my dead drive. The EXABYTE VXA-3(20) is the new drive
    BE will not recognize. I added the 29160 card tonight. Previously the Exabyte
    drive was attached to the onboard SCSI adapter, but with the same result.


    Any advice would be much appreciated. Thanks.

    "Chris" wrote:
    >Ken Berg wrote:
    >
    >>
    >> Version 9.0.4202 for Netware
    >> I added an Exabyte VXA-320 drive. The server sees the drive and
    >> BEDIAG sees it as well. However, scan for new devices doesn't find
    >> the new drive. I installed the latest drivers in the BKUPEXEC\NLMS
    >> folder and restarted.
    >>
    >> I found a TID for 8.5 that says you have to delete the hardware
    >> database and restart BE for new hardware to be found. However,
    >> BKUPEXEC\PM does not exist. I do have BKUPEXEC\MM. Are they the same
    >> thing?

    >
    >Yes. Try the following to see if this helps:
    >
    >1. BESTOP
    >2. Rename :\bkupexec\mm to mm.old
    >3. BESTART
    >
    >If that doesn't help, as Barry said, please post back with the results
    >of typing LIST STORAGE ADAPTERS at the server console.
    >
    >Chris
    >



  5. Re: New hardware not recognized

    Ken Berg wrote:

    >
    > Renaming the MM directory didn't work. Here's the results of list
    > storage adapters:
    >
    > IWHC_01:list storage adapters
    > 0x00 [V651-A0] PERC2 Host Aadapter Module [slot 10005]
    > 0x08 [V651-A0-D6:0] Unbound Device Object
    > 0x01 [V651-A1] PERC2 Host Adapter Module [slot 10005]
    > 0x07 [V651-A1-D1:0] DELL RAID Device 0:01 rev:1.0
    > 0x06 [V651-A1-D0:0] DELL RAID Device 0:00 rev:1.0
    > 0x02 [V651-A2] PERC2 Host Adapter Module [slot 10005]
    > 0x03 [V651-A3] PERC2 Host Adapter Module [slot 10005]
    > 0x04 [V651-A4] PERC2 Host Adapter Module [slot 10005]
    > 0x05 [V651-A5] PERC2 Host Adapter Module [slot 10005]
    > 0x09 [V321-A6] Adaptec AIC-7899 - Ultra160 SCSI [slot 10003]
    > 0x0A [V312-A7] Adaptec SCSI Adapter [slot 10004]
    > 0x0C [V312-A7-D6:0] BNCHMARKDLT1 391B
    > 0x0B [V312-A7-D5:0] NEC CD-ROM DRIVE:466 rev:1.06
    > 0x13 [V321-A8] Adaptec SCSI Card 29160 - Ultra160 SCSI [slot 1]
    > 0x14 [V321-A8-D2:0] EXABYTE VXA-3 310E
    >
    > The BNCHMARKDLT1 is my dead drive. The EXABYTE VXA-3(20) is the new
    > drive BE will not recognize. I added the 29160 card tonight.
    > Previously the Exabyte drive was attached to the onboard SCSI
    > adapter, but with the same result.
    >
    >
    > Any advice would be much appreciated. Thanks.


    Looks like you need to install the up-to-date driver set:

    http://support.veritas.com/docs/282047


+ Reply to Thread