Forum Discussion

bandit61's avatar
bandit61
Level 6
10 years ago
Solved

BE14 performance issues after replacing drive

We use a neo400 with 3 drives. Already had to replace one drive without any problems, just setting the firmware straight for all 3. Now I had to replace another drive and after putting all backup-jobs back, still got some severe performance-issues with the replacement-drive.

Normally around 11h and with 2000mb/Min. Now still running after 12h with a performance of 1000MB/Min and still got 7 servers to backup out of 21 (daily-3.jpg). I set all drives to firmware E6R3 and the neo214 is on C.40, with Backup Exec 14 is this the right settings or do I have to change (neo214.jpg & neo214_tapedrives.jpg). 

What still bother me is, that after rebooting both server CAS & MMS and several times the be-services, there are still differences in the device manager show-up (cas_be14.jpg & mms_be14.jpg).

 

 

  • Now after changing the chassis of the library as well, we had 3 nights of successful backup-jobs. It was hardware-failure together with a locking a cartridge in the drive. 

  • C70 seems to be the latest firmware as per http://ftp.overlandstorage.com/Firmware/Neo_Series/NEOs/NEO400s/With_IBM_Drives/

    Are you using Symantec driver for the replaced tape drive ? Do you get the usual throughput if the job runs to the other tape drives ?

  • The other 2 drives are performing okay, all 3 drives use the same drivers

    Symantec 12.2.2008  Version 5.1.37.0

    even the rep-drive not showing up as SCSI Sequential drive on the CAS.

  • updated the library to C70, will see what happens with performance during next night-backup. will update tomorrow morning.

  • What still bother me is, that after rebooting both server CAS & MMS and several times the be-services, there are still differences in the device manager show-up (cas_be14.jpg & mms_be14.jpg).

    The appearance of the tape drives in Windows Device manager is controlled by the driver bound to the tape drive.  This is different than the User-Mode driver that is actually used by BE to control the LTO drives (although there could be some weird interactions with mis-behaving bound drivers)

    What operating system are you using?

    If you are using an OS prior to windows 2012, then run tapeinst.exe and make sure to select the checkbox for "delete entries for tape evices that are unavailable, removed or turned off".  then reboot the server and check Windows Device Manager.

    If you are still having performance issues with only one tape drive after making sure they all have the same firmware and drivers bound, then you should consider running the tape vendor diagnostics to validate the drive.  Or do more testing to make sure it isn't just a bad media.

     

     

  • Performance still only half of what it was before. Used different tapes as before, so wouldn't blame the tapes.

     

    CAS & MMS are both on W2008R2, so will follow Larry's advice and see what will happen.

  • run tapeinst.exe result on both cas&mms: result_both_cas_mms.jpg

    1 missing device on the cas: cas_missing.jpg

    3 devices okay, look like: cas_3.jpg

    device drivers on both look same: neo400s.jpg and tape.jpg

    but cas still showing the newly added drive as IBM ULTRIUM-HH6, the other 2 as IBM ULTRIUM-HH6 Sequential Device.

     

  • Delete the "missing device" and restart BE services.

    Can you post your adamm.log files?

  • Set the library back to firmware C40. / 3.20e and all 3 drives to D8E5. rebooted library, cas and mms. now the performance looks okay (during day), but only night-backup will show the truth. Deleted the "missing" device on both cas/mms and now you can't add any device to the storage pool, but you'll find the "missing" in the 2 adamm-logfiles.

    still the library shows attention in the webgui and the 3 led above the display is on and the "!" is beneath the 4 (drive), where i inserted the fault drive to release the stuck tap with the reject button. Not sure if this device will appear again, if we reboot on fo the 3 (library, cas, mms).

     

  • After several failed/recovered backup-jobs, we agreed with the support of our tape-library to change the complete chassis. This will happen on thrusday and should solve the issue. Will update this post then.

  • Now after changing the chassis of the library as well, we had 3 nights of successful backup-jobs. It was hardware-failure together with a locking a cartridge in the drive.