BE15.0.3 and Win2012R2; no tapeinst.exe ?

tapeinst.exe was removed because there is no need to install kernel-mode drivers for the newer OS, like Server 2012.

Your tape library should appear in the Windows Device Manager as an Unknown Medium Changer with a Microsoft driver and the tape drive should have a Symantec driver.

Have you tried deleting and re-installing the tape library and tape drive in the BE console?  If not try this

1) On the Storage tab,  delete all occurances of the tape drives and tape libraries

2) Stop the media server and the library

3) Start the tape library

4) Start the media server

5) Ensure that the library and tape drive is recognised and functioning correctly in the Windows Device Manager. The library should appear as an Unknown Medium Changer with a Microsoft driver and the tape drive should have a Symantec driver.

6) Target your jobs to some other device, save it and then target it to the tape library again.

Thanks for your advice.

I did delete the drives from BE and executed a power cycle. But have not done this with the library because all the job descriptions would be impacted. Seen all other actions did not help I'll go for deleting all drives and libraries from BE and do a power cycle.

 

Removing all tape libraries and drives fom BE, and power cycling did not help.

I still have Microsoft mentioned as driver provider for the tape drives.

Try installing the manufacturer's drivers manually then and see if this helps...

Thanks!

Thanks for your advice.

One of my first attempts to rectify was to use the drivers offered by Dell (vendor) and those of the manufacturer (IBM).

Can someone acknowledge that the driver provider (if tape drive installations by BackupExec is performed correctly) should read 'Symantec', in my case it always reads Microsoft (unless I install the IBM drivers) ?

 

Yes it would show Symantec as the driver.

 

This is a long shot, but try using the procedure in this document to see whether you can get the Symantec drivers.

http://www.veritas.com/docs/000037173

Thanks for your advice.

I've used it to try to switch the tape drive driver, but no other driver is available. Also forcing Windows to search in the Backup Exec directory does not offer another driver.

Maybe the correct drivers are installed, and Microsoft is the correct provider for library and drives, and the bandwith cap is caused by the SAS hardware ?

I have added a screen shot of the hardware list and driver details (same for libary and drives).

All BE certification tests are done with Symantec drivers. If you use other drivers, there is no guarantee that you would not encounter problems

Can someone acknowledge that the driver provider (if tape drive installations by BackupExec is performed correctly) should read 'Symantec', in my case it always reads Microsoft (unless I install the IBM drivers) ?

 

With Windows Server 2012 and up, there is no tapeinst.exe and there are no Symantec drivers to bond to the tape drive.  Generally, the Microsoft driver is suggested for the tape drives.  So, you should be OK there.

There is some good info at the very top of the HCL about drivers.  https://www.veritas.com/support/en_US/article.000024527

 

I've recently installed the latest firmware to our (iSCSI) Dell TL4000 and LTO6 drives. Ever since backups have limited (228MB/min) throughput.

If this is the ONLY thing that has changed, have you investigated going back to the old firmware to see if maybe the new firmware is broken?  What speed were you getting before, when things were good?

Are you using the Dell iSCSI blade for that library or some other ISCSI-SAS converter?

What type of firmware did you install?  for the iSCSI blade? the library?  the drives?  all of the above?

Since the library and drives are pretty popular, I wouldn't be too worried about those, but there are no guarantees.  The iSCSI blade is not as common, so that would be my area of focus.  Any chance that you could test this temporarily without using iSCSI and only using simple SAS?