Forum Discussion

hippototamus's avatar
hippototamus
Level 3
9 years ago

Library went offline after repair. Veritas support cannot help...

Hello.

Im really stuck here, so hoping to find some answers here. There were some problems with creating or editing backup jobs, so the support told me to try repair installation of Backup Exec 15. Before that I insalled FP4. After the repair installation, Robotic Library and Tape Drives went offline, so all backups what goes to tapes now fails. Its been a week of support calls but they cannot find the problem, and looks like they are out of ideas.

I have already checed the drivers : Medium Changer device - Unknown Medium Changer (MS drivers) For Tape drives - its symantec drivers. Also checked group polcy settings - no policy enabled that disables writing on tapes. Tried to reinstall the drivers. Tried to do the power off cycle of the server and the library. Nothing helps. Error messages I got are:

Backup Exec Alert: Storage Error
(Server: "BACKUPEXEC") Backup Exec was unable to initialize and communicate with the device \\.\Tape1 [HP      Ultrium 6-SCSI  33ES] (The system cannot find the file specified.).  Click the link below for more information on how to diagnose the problem. 

Backup Exec Alert: Storage Error
(Server: "BACKUPEXEC") Backup Exec was unable to initialize and communicate with the device  [STK     SL150           0225] (The system cannot find the path specified.).  Click the link below for more information on how to diagnose the problem. 

Backup Exec Alert: Storage Error
(Server: "BACKUPEXEC") Backup Exec was unable to initialize and communicate with the device \\.\Tape0 [HP      Ultrium 6-SCSI  33ES] (The system cannot find the file specified.).  Click the link below for more information on how to diagnose the problem.

ADAMM configuration warning.
The device driver may not be installed for device :
 Identifier : STK     SL150           0225.
 Type : MediumChangerPeripheral.

If I try to run the backupJob:

(Server: "BACKUPEXEC") (Job: "xxxx") xxx -- The job failed with the following error: The operation failed to acquire the minimum number of drives and media needed.

 

PvLSvl Log:

14    PVLSVR    5420    5/6/2016 12:14:25 PM    3040    PvlDevice::ReadDeviceScsiInquiryInfo()
        0003:0000:0011:0000  "HP      Ultrium 6-SCSI  33ES", "\\.\Tape1"
15    PVLSVR    5420    5/6/2016 12:14:25 PM    3040    PvlDevice::ReadDeviceScsiInquiryInfo() - OpenHandle
        ERROR = 0x00000005 (ERROR_ACCESS_DENIED), Device Path = "\\.\Tape1"
17    PVLSVR    5420    5/6/2016 12:14:25 PM    3040    PvlDevice::ReadDeviceScsiInquiryInfo() - OpenHandle
        ERROR = 0x00000003 (ERROR_PATH_NOT_FOUND), Device Path = ""
18    PVLSVR    5420    5/6/2016 12:14:25 PM    3040    PvlDevice::ReadDeviceScsiInquiryInfo()
        0003:0000:0021:0000  "HP      Ultrium 6-SCSI  33ES", "\\.\Tape0"
19    PVLSVR    5420    5/6/2016 12:14:25 PM    3040    PvlDevice::ReadDeviceScsiInquiryInfo() - OpenHandle
        ERROR = 0x00000005 (ERROR_ACCESS_DENIED), Device Path = "\\.\Tape0"

 

How and where can I check the permissions on the Tape0 and Tape1 as it cleary states that somewhere it does not has access anymore.

 

Thanks and hoping for an answer.

 

 

15
Backup and Recovery
Backup Exec
Windows Server (2003-2008)
  • Larry_Fine's avatar
    Larry_Fine
    9 years ago

    As in Veritas manual they state that tape drivers should use symantec drivers and the medium changer should use Microsoft default one. As it turn out in my scenario Backup Exec detects Tapedrive only when the tape drives have no drivers installed at all (not the Hp or symantec)  - in device manager they show as Other Devices and Driver Provider is Unknown.

    So when Veritas support did a repair installation on BackupExec the installation reinstalled the drivers as well and broke the link betweent backpexec and tape drives.

    That is weird and doesn't make sense to me.  With Windows 2008, BE should be installing and using Symantec drivers (as seen in windows Device Manager).  With Windows Server 2012, the situation is different, but your adamm.log shows Server 2008.

    Here is what the HCL says, which I have found to be accurate:

    Some notes about drivers: Veritas Kernel-mode Tape drivers and tapeinst.exe are no longer installed if Backup Exec 15 is installed on Windows Server 2012 or later. There are no devices on this Backup Exec 15 Hardware Compatibility List (HCL) that require Veritas Kernel-mode drivers. USB tape devices still require a Microsoft or vendor Kernel-mode driver, in addition to the Veritas User-mode driver. Users of very old, unsupported, tape devices should investigate and test before using Windows Server 2012 to determine the functionality as kernel-mode drivers may be required. All supported tape devices are now accessed by Veritas User-mode drivers. Most tape devices have been accessed by User-mode drivers for multiple previous versions of Backup Exec.

    User-mode drivers are not visible in the Windows Device Manager. When no Kernel-mode drivers are installed, the Windows Device Manager may show the tape drive with a yellow exclamation mark. This is acceptable and does NOT prevent the device from being used with Backup Exec and the User-mode drivers. Kernel-mode drivers from Microsoft or the tape hardware vendor are generally acceptable to be installed. Backup Exec will continue to access the tape devices via User-mode drivers.

    Tapeinst.exe is the program that installs Veritas Kernel-mode tape class drivers. When using Windows Server 2008 R2 or earlier, tapeinst.exe can be invoked manually or via the "Install Tape Device Drivers" wizard (under the "Configure Storage" menu). When using Windows Server 2012 or later, the ability to run the "Install Tape Device Drivers" wizard (under the Configure Storage menu) is no longer present and is not needed.

    As long as you are working now, you should be in good shape.

  • CraigV's avatar
    CraigV
    Moderator
    9 years ago

    Hi,


    This is a community platform so people help when they're able too.

    Have you tried to remove the library completely from Windows and BE, and then disconnect from the server?

    Once done, restart the server and make sure it doesn't show in Windows.

    Shut the server down, reconnect the library and start it up before the server. Then run the driver installation.

    Thanks!

  • Colin_Weaver's avatar
    Colin_Weaver
    Moderator
    9 years ago

    Just if info the Access Denied error code (0005) is often retured when a request for something cannot return the item - that does not always mean a security denial, it can mean the item being asked for is physically not there or the route to the device is not available.

    As such the fact that it is against an Open Handle request is perhaps more important as that might mean

    - something else already has control of the device and is not sharing access

    - the device is not connected properly or there is a fault  with the connection

    - something is specifically denying access (OK so this would be permissions or security)

    - there is a problem with the tape/library hardware itself

    - there is a problem with the OS or drivers within the OS that access the hardware

     

    I would start by trying to test the hardware with tools from the hardware vendor (with the BE services stopped)

     

     

     

     

     

  • Larry_Fine's avatar
    Larry_Fine
    Level 6
    9 years ago

    Is your tape library FC or SAS?  can you post your whole adamm.log?  or at least the most recent boot cycle of it?

  • hippototamus's avatar
    hippototamus
    Level 3
    9 years ago

    Hi, thanks for Your replies.

    As the problem appeared just after backupexec repair installation I doubt there are some hardware problems with the tape drive. And the backupexec service is the only one what is using the Robotic library.

    Tape library is SAS.

    Adamm from last boot:

    [03364] 05/06/16 15:38:34.986 Adamm Log Started! ("BACKUPEXEC", 1000, {CEA7EBCB-6F23-436F-801C-F00191D6A1B6})

Adamm Info: Version 14.2, Build 1180, 64bit

OS Info: Windows Server 2008, Build 6002, Service Pack 2

RSM Service Status: Not Running

Database Driver Info: SQLSRV32.DLL, 06.00.6002
Database Server Info: Server Name = "BACKUPEXEC", Active Node = ""
Database Connection String: "DRIVER=SQL Server;SERVER=backupexec\BkupExec;DATABASE=BEDB;App=BEWS PVL"

DateTimeSync: Local = 2016/05/06 15:38:34, System = 2016/05/06 14:38:34 GMT, Database = 2016/05/06 14:38:34 GMT

Shared Storage Authorization: No
TSM Authorization: No
SPO Installed and Authorized: No
SPO Limited Installed and Authorized: No
Dell SPO: Yes
Library Expansion Options: 1
VTL Options: 0

[03364] 05/06/16 15:38:35.037 Not adjusting max system cache file size.

[04280] 05/06/16 15:38:35.073 Waiting on PDDE service start (3600000 milliseconds)
[04280] 05/06/16 15:38:35.073 PDDE service has not started; continuing...
Treat all LTO devices as if they are in UMD certified device list: DioAllLto = 0x0001
Use UMD certified device list: DioDrivers = 0x0002

[04280] 05/06/16 15:38:36.280 Read Device Records - start

[04280] 05/06/16 15:38:36.347 Read Device Records - end

[04280] 05/06/16 15:38:36.427 Initializing Storage Manager component processing
[04280] 05/06/16 15:38:36.427 iSCSI Discovery - start

iSCSI initiator software version 6.0.6002

No persistent iSCSI target logins are set up

No iSCSI target mappings discovered

[04280] 05/06/16 15:38:36.429 iSCSI Discovery - end

[04280] 05/06/16 15:38:36.432 Registry SCSI Discovery - start

[04280] 05/06/16 15:38:36.434 Registry SCSI Discovery - end

[04280] 05/06/16 15:38:36.475 Device Name Discovery - start

[04280] 05/06/16 15:38:36.476 Backup Exec was unable to initialize and communicate with the device \\.\Tape0 (Access is denied.).  Click the link below for more information on how to diagnose the problem.
[04280] 05/06/16 15:38:36.476 Backup Exec was unable to initialize and communicate with the device \\.\Tape1 (Access is denied.).  Click the link below for more information on how to diagnose the problem.
[04280] 05/06/16 15:38:36.477 Device Name Discovery - end

[04280] 05/06/16 15:38:36.477 B2D Discovery - start

[04280] 05/06/16 15:38:36.480 B2D Discovery - end

[04280] 05/06/16 15:38:36.480 USB/Firewire Discovery - start

[04280] 05/06/16 15:38:36.482 USB/Firewire Discovery - end

[04280] 05/06/16 15:38:36.482 Iomega REV Discovery - start

[04280] 05/06/16 15:38:36.482 Iomega REV Discovery - end

[04280] 05/06/16 15:38:36.484 Device Registry:

Scsi Address
Prt :Bus :Tar :Lun   Attributes
-------------------  -------------------------------------------------------------------------------

0002:0000:0000:0000  "LSI_SAS", (Port Driver)

-------------------  -------------------------------------------------------------------------------

0003:0000:0000:0000  "LSI_SAS", (Port Driver)
0003:0000:0011:0000  "HP      Ultrium 6-SCSI  33ES", (Tape Device), "\\.\Tape1"
0003:0000:0011:0001  "STK     SL150           0225", (Changer Device), ""
0003:0000:0021:0000  "HP      Ultrium 6-SCSI  33ES", (Tape Device), "\\.\Tape0"

-------------------  -------------------------------------------------------------------------------

0004:0000:0000:0000  "megasas", (Port Driver)

-------------------  -------------------------------------------------------------------------------

0005:0000:0000:0000  "iScsiPrt", (Port Driver)

-------------------  -------------------------------------------------------------------------------

9999:0112:0018:0000  "FIXEDB2DDevice          1.00", "\\.\Bkup2Dsk"

-------------------  -------------------------------------------------------------------------------

[04280] 05/06/16 15:38:36.484 Read NDMP Server Records - start

[04280] 05/06/16 15:38:36.495 Read NDMP Server Records - end

[04280] 05/06/16 15:38:36.495 Read OST Server Records - start

[04280] 05/06/16 15:38:36.505 Read OST Server Records - end

[04280] 05/06/16 15:38:36.506 DeviceIo Discovery - start

[04280] 05/06/16 15:38:41.250 DeviceIo Discovery - end

[04280] 05/06/16 15:38:41.250 DeviceIo Devices:

Scsi Address
Prt :Bus :Tar :Lun   Attributes
-------------------  -------------------------------------------------------------------------------

-------------------  -------------------------------------------------------------------------------

[04280] 05/06/16 15:38:41.251 PnP Device Paths:

Scsi Address
Prt     :Bus     :Tar     :Lun       Device Path
-----------------------------------  ---------------------------------------------------------------

-----------------------------------  ---------------------------------------------------------------

[04280] 05/06/16 15:38:41.251 Read Device Inquiries - start

[04280] 05/06/16 15:38:41.251 Backup Exec was unable to initialize and communicate with the device \\.\Tape1 [HP      Ultrium 6-SCSI  33ES] (Access is denied.).  Click the link below for more information on how to diagnose the problem.
[04280] 05/06/16 15:38:41.252 Backup Exec was unable to initialize and communicate with the device  [STK     SL150           0225] (The system cannot find the path specified.).  Click the link below for more information on how to diagnose the problem.
[04280] 05/06/16 15:38:41.252 Backup Exec was unable to initialize and communicate with the device \\.\Tape0 [HP      Ultrium 6-SCSI  33ES] (Access is denied.).  Click the link below for more information on how to diagnose the problem.
[01952] 05/06/16 15:38:42.479 [StorageManagerMatador::Initialize()] Error reading registry value to get location of XML file with provisioning parameters: 0x2
[01952] 05/06/16 15:38:42.479 [StorageManagerMatador::Initialize()] The program will use default values for provisioning parameters: 0x0
[01952] 05/06/16 15:39:01.541 [StorageManager::RemoveUnusedLocalDisksFromDB] Results:
0 non-present unconfigured local disks were deleted
0 local disk parent objects with no local disks were deleted

    adamm.log before repair job, when Library was working and was online:

    [02912] 04/26/16 19:08:24.532 Adamm Log Started! ("BACKUPEXEC", 1000, {CEA7EBCB-6F23-436F-801C-F00191D6A1B6})

Adamm Info: Version 14.2, Build 1180, 64bit

OS Info: Windows Server 2008, Build 6002, Service Pack 2

RSM Service Status: Not Running

Database Driver Info: SQLSRV32.DLL, 06.00.6002
Database Server Info: Server Name = "BACKUPEXEC", Active Node = ""
Database Connection String: "DRIVER=SQL Server;SERVER=backupexec\BkupExec;DATABASE=BEDB;App=BEWS PVL"

DateTimeSync: Local = 2016/04/26 19:08:24, System = 2016/04/26 18:08:24 GMT, Database = 2016/04/26 18:08:24 GMT

Shared Storage Authorization: No
TSM Authorization: No
SPO Installed and Authorized: No
SPO Limited Installed and Authorized: No
Dell SPO: Yes
Library Expansion Options: 1
VTL Options: 0

[02912] 04/26/16 19:08:27.077 Not adjusting max system cache file size.

[01096] 04/26/16 19:08:27.186 Waiting on PDDE service start (3600000 milliseconds)
[01096] 04/26/16 19:08:27.186 PDDE service has not started; continuing...
Treat all LTO devices as if they are in UMD certified device list: DioAllLto = 0x0001
Use UMD certified device list: DioDrivers = 0x0002

[01096] 04/26/16 19:08:34.696 Read Device Records - start

[01096] 04/26/16 19:08:36.398 Read Device Records - end

[01096] 04/26/16 19:08:38.396 Initializing Storage Manager component processing
[01096] 04/26/16 19:08:38.396 iSCSI Discovery - start

iSCSI initiator software version 6.0.6002

No persistent iSCSI target logins are set up

No iSCSI target mappings discovered

[01096] 04/26/16 19:08:38.443 iSCSI Discovery - end

[01096] 04/26/16 19:08:38.443 Registry SCSI Discovery - start

[01096] 04/26/16 19:08:38.630 Registry SCSI Discovery - end

[01096] 04/26/16 19:08:39.052 Device Name Discovery - start

[01096] 04/26/16 19:08:53.275 Device Name Discovery - retry - 1 names missing, 75 retries left

[01096] 04/26/16 19:09:08.497 Device Name Discovery - retry - 1 names missing, 60 retries left

[01096] 04/26/16 19:09:23.719 Device Name Discovery - retry - 1 names missing, 45 retries left

[03220] 04/26/16 19:09:31.650 [StorageManagerMatador::Initialize()] Error reading registry value to get location of XML file with provisioning parameters: 0x2
[03220] 04/26/16 19:09:31.650 [StorageManagerMatador::Initialize()] The program will use default values for provisioning parameters: 0x0
[01096] 04/26/16 19:09:38.941 Device Name Discovery - retry - 1 names missing, 30 retries left

[01096] 04/26/16 19:09:54.163 Device Name Discovery - retry - 1 names missing, 15 retries left

[01096] 04/26/16 19:10:09.385 Device Name Discovery - end

[01096] 04/26/16 19:10:09.385 B2D Discovery - start

[01096] 04/26/16 19:10:09.416 B2D Discovery - end

[01096] 04/26/16 19:10:09.416 USB/Firewire Discovery - start

[01096] 04/26/16 19:10:09.416 USB/Firewire Discovery - end

[01096] 04/26/16 19:10:09.416 Iomega REV Discovery - start

[01096] 04/26/16 19:10:09.416 Iomega REV Discovery - end

[01096] 04/26/16 19:10:09.416 Device Registry:

Scsi Address
Prt :Bus :Tar :Lun   Attributes
-------------------  -------------------------------------------------------------------------------

0002:0000:0000:0000  "LSI_SAS", (Port Driver)

-------------------  -------------------------------------------------------------------------------

0003:0000:0000:0000  "LSI_SAS", (Port Driver)
0003:0000:0011:0000  "HP      Ultrium 6-SCSI  33ES", (Tape Device), ""
0003:0000:0011:0001  "STK     SL150           0225", (Changer Device), ""
0003:0000:0021:0000  "HP      Ultrium 6-SCSI  33ES", (Tape Device), ""

-------------------  -------------------------------------------------------------------------------

0004:0000:0000:0000  "megasas", (Port Driver)

-------------------  -------------------------------------------------------------------------------

0005:0000:0000:0000  "iScsiPrt", (Port Driver)

-------------------  -------------------------------------------------------------------------------

9999:0112:0018:0000  "FIXEDB2DDevice          1.00", "\\.\Bkup2Dsk"

-------------------  -------------------------------------------------------------------------------

[01096] 04/26/16 19:10:09.416 Read NDMP Server Records - start

[01096] 04/26/16 19:10:09.463 Read NDMP Server Records - end

[01096] 04/26/16 19:10:09.463 Read OST Server Records - start

[01096] 04/26/16 19:10:09.541 Read OST Server Records - end

[01096] 04/26/16 19:10:09.541 DeviceIo Discovery - start

[01096] 04/26/16 19:10:15.099 DeviceIo Discovery - end

[01096] 04/26/16 19:10:15.099 DeviceIo Devices:

Scsi Address
Prt :Bus :Tar :Lun   Attributes
-------------------  -------------------------------------------------------------------------------

0003:0000:0011:0001  DeviceIo[01]: "STK     SL150           464970G+1502SY3762", Cert=Y, "\\.\Scsi3:"
0003:0000:0011:0000  DeviceIo[02]: "HP      Ultrium 6-SCSI  HUJ4502L0A", Cert=Y, "\\.\Scsi3:"
0003:0000:0021:0000  DeviceIo[03]: "HP      Ultrium 6-SCSI  HUJ4482ELB", Cert=Y, "\\.\Scsi3:"

-------------------  -------------------------------------------------------------------------------

[01096] 04/26/16 19:10:15.099 PnP Device Paths:

Scsi Address
Prt     :Bus     :Tar     :Lun       Device Path
-----------------------------------  ---------------------------------------------------------------

-----------------------------------  ---------------------------------------------------------------

[01096] 04/26/16 19:10:15.099 Read Device Inquiries - start

[01096] 04/26/16 19:10:15.099 Device: \\.\Scsi3:
[01096] 04/26/16 19:10:15.693 Device: \\.\Scsi3:
[01096] 04/26/16 19:10:16.301 Device: \\.\Scsi3:
[01096] 04/26/16 19:10:16.348 Device: \\.\Bkup2Dsk

[01096] 04/26/16 19:10:17.020 Read Device Inquiries - end

[01096] 04/26/16 19:10:17.020 Serialize Devices:

[01096] 04/26/16 19:10:17.472 Device Discovery:

[01096] 04/26/16 19:10:17.472 Device Driver Status:

Scsi Address
Prt :Bus :Tar :Lun   Status
-------------------  -----------------------------------------------

0003:0000:0011:0000  HP      Ultrium 6-SCSI  33ES [HP      Ultrium 6-SCSI  HUJ4502L0A] (White List User Mode Driver)
0003:0000:0011:0001  STK     SL150           0225 [STK     SL150           464970G+1502SY3762] (White List User Mode Driver)
0003:0000:0021:0000  HP      Ultrium 6-SCSI  33ES [HP      Ultrium 6-SCSI  HUJ4482ELB] (White List User Mode Driver)
9999:0112:0018:0001  FIXEDB2DDevice          1.00 [FIXEDB2DDevice           {7EFB1B46-A306-4879-B51F-3F7599D653F8}]
-------------------  -----------------------------------------------

Scsi Address
Prt :Bus :Tar :Lun   Attributes
-------------------  -------------------------------------------------------------------------------

0003:0000:0011:0000  Device Name             "\\.\Scsi3:"
                     Primary Inquiry         "HP      Ultrium 6-SCSI  33ES"
                     Serial Number           "HP      Ultrium 6-SCSI  HUJ4502L0A"
                     Device Flags            UMD, SCSI, SN(TYPE 0)
                     Device State            3, Online

                     Device IDs              1021, {94186395-FE19-4F1E-8408-A4EA18EC8A48}
                     Device Name             "Tape drive 0001"
                     Device Type             134283265, "LTO 64K (64K,10,0,E,HU)"
                     Device Features         0x005BFA7F: PB,SFB,SRB,WFM,SFF,SRM,PEOD,EL,LU,E,SBS,DC,SDC,TA,HU,RR,W,EN
                     Device Element          1025, 0
                     Device Block Limits     512 min, 1048576 max
                     Device Hard Errors      0 write, 0 read
                     Device Soft Errors      88 write, 867 read

0003:0000:0011:0001  Device Name             "\\.\Scsi3:"
                     Primary Inquiry         "STK     SL150           0225"
                     Serial Number           "STK     SL150           464970G+1502SY3762"
                     Device Flags            UMD, SCSI, SN(TYPE 0), SN(ELEMENT)
                     Device State            3, Online

                     Device IDs              1025, {47040888-95F8-4748-AD97-4B800A8B7A35}
                     Device Name             "ORACLE SL150"
                     Device Type             2131755008, "CHANGER FS=1"
                     Device Features         0x00006200: PP,RMP,RRD
                     1st Slot Number         1
                     Number Of Slots         30
                     Portal Slots            4
                     Import/Export           Robotic
                     Drives                  2

                     Drive Element 0         1021, "HP      Ultrium 6-SCSI  HUJ4502L0A"
                     Drive Element 1         1023, "HP      Ultrium 6-SCSI  HUJ4482ELB"

0003:0000:0021:0000  Device Name             "\\.\Scsi3:"
                     Primary Inquiry         "HP      Ultrium 6-SCSI  33ES"
                     Serial Number           "HP      Ultrium 6-SCSI  HUJ4482ELB"
                     Device Flags            UMD, SCSI, SN(TYPE 0)
                     Device State            3, Online

                     Device IDs              1023, {8E098454-6983-4DCA-BE97-E023DD50AEA5}
                     Device Name             "Tape drive 0002"
                     Device Type             134283265, "LTO 64K (64K,10,0,E,HU)"
                     Device Features         0x005BFA7F: PB,SFB,SRB,WFM,SFF,SRM,PEOD,EL,LU,E,SBS,DC,SDC,TA,HU,RR,W,EN
                     Device Element          1025, 1
                     Device Block Limits     512 min, 1048576 max
                     Device Hard Errors      0 write, 0 read
                     Device Soft Errors      56 write, 1509 read
  • Cupis's avatar
    Cupis
    Level 4
    9 years ago

    Hi,

    I see you are using a Oracle Tape Library. Check if they have any diagnostic tools. I use HP Library and Tape tools which has some diagnostic tools to run the Library through the sprints. Just read carefully what you doing on each action, as I have found that certain diagnostic runs can potentially erase your tapes to do Read/Write Tests.

    You should also see in Windows Device Manager the Medium Changer as well as the Tape drives listed. The Medium changer is detected through one of the tape drives, so it should list all the drives that are installed. From there I would try installing the Manufacturers Drivers.

    Basically the drive and medium changer must appear healthy on Windows and their diagnostic tools before you start troubleshooting anything through Backup Exec itself.

    Regards,

    Cupis

  • hippototamus's avatar
    hippototamus
    Level 3
    9 years ago

    Thanks for all your replies. Finally found a what caused the problem, and it was a hard to find easy fix :)


    As in Veritas manual they state that tape drivers should use symantec drivers and the medium changer should use Microsoft default one. As it turn out in my scenario Backup Exec detects Tapedrive only when the tape drives have no drivers installed at all (not the Hp or symantec)  - in device manager they show as Other Devices and Driver Provider is Unknown.

    So when Veritas support did a repair installation on BackupExec the installation reinstalled the drivers as well and broke the link betweent backpexec and tape drives.

    Thanks for your support :)

  • Larry_Fine's avatar
    Larry_Fine
    Level 6
    9 years ago

    As in Veritas manual they state that tape drivers should use symantec drivers and the medium changer should use Microsoft default one. As it turn out in my scenario Backup Exec detects Tapedrive only when the tape drives have no drivers installed at all (not the Hp or symantec)  - in device manager they show as Other Devices and Driver Provider is Unknown.

    So when Veritas support did a repair installation on BackupExec the installation reinstalled the drivers as well and broke the link betweent backpexec and tape drives.

    That is weird and doesn't make sense to me.  With Windows 2008, BE should be installing and using Symantec drivers (as seen in windows Device Manager).  With Windows Server 2012, the situation is different, but your adamm.log shows Server 2008.

    Here is what the HCL says, which I have found to be accurate:

    Some notes about drivers: Veritas Kernel-mode Tape drivers and tapeinst.exe are no longer installed if Backup Exec 15 is installed on Windows Server 2012 or later. There are no devices on this Backup Exec 15 Hardware Compatibility List (HCL) that require Veritas Kernel-mode drivers. USB tape devices still require a Microsoft or vendor Kernel-mode driver, in addition to the Veritas User-mode driver. Users of very old, unsupported, tape devices should investigate and test before using Windows Server 2012 to determine the functionality as kernel-mode drivers may be required. All supported tape devices are now accessed by Veritas User-mode drivers. Most tape devices have been accessed by User-mode drivers for multiple previous versions of Backup Exec.

    User-mode drivers are not visible in the Windows Device Manager. When no Kernel-mode drivers are installed, the Windows Device Manager may show the tape drive with a yellow exclamation mark. This is acceptable and does NOT prevent the device from being used with Backup Exec and the User-mode drivers. Kernel-mode drivers from Microsoft or the tape hardware vendor are generally acceptable to be installed. Backup Exec will continue to access the tape devices via User-mode drivers.

    Tapeinst.exe is the program that installs Veritas Kernel-mode tape class drivers. When using Windows Server 2008 R2 or earlier, tapeinst.exe can be invoked manually or via the "Install Tape Device Drivers" wizard (under the "Configure Storage" menu). When using Windows Server 2012 or later, the ability to run the "Install Tape Device Drivers" wizard (under the Configure Storage menu) is no longer present and is not needed.

    As long as you are working now, you should be in good shape.