MSL4048 LTO6 Library

[Shoghi]

Hi to all!!!

We recently have adquired a new MSL4048 library (LTO6) to use with netbackup, the media server sees the library without problems, all drives are ok, aparently.

When we try to configure a new or old backup definition to use the new library it takes about a minute to mount a tape, and after some time the drive goes down, We have tried the drive test from NB Gui and it also fails.

Do we have to do something else to configure this library with netbackup?, perhaps We missed something from the documentation (again).

This a log from drive test:

11/12/2015 10:49:30 AM - requesting resource DRIVE07:{3,0,3,0}:NetBackup:__ANY__
11/12/2015 10:49:30 AM - reserving resource DRIVE07:{3,0,3,0}:NetBackup:__ANY__
11/12/2015 10:49:30 AM - reserved resource 000007
11/12/2015 10:49:30 AM - granted resource 000007
11/12/2015 10:49:30 AM - granted resource DRIVE07
11/12/2015 10:49:30 AM - begin 
11/12/2015 10:49:32 AM - Info bptm(pid=8032) start            
11/12/2015 10:49:32 AM - Info bptm(pid=8032) Waiting for mount of media id 000007 (copy 1) on server sernb03 
11/12/2015 10:49:32 AM - mounting 000007
11/12/2015 10:49:32 AM - Info bptm(pid=8032) INF - Waiting for mount of media id 000007 on server sernb03 for reading.
11/12/2015 10:51:16 AM - mounted; mount time: 0:01:44
11/12/2015 10:51:16 AM - Info bptm(pid=8032) EXITING with status 0 <----------        
media manager failure(810)

Thanks in advance.

[D_Flood]

What do you have for timeout values in the properties of your Master and any Media Servers - both the ones under "Media" and the "Media Mount Timeout" under "Timeouts"?

[RiaanBadenhorst · Accepted solution]

Do you have the latest device mappings installed? https://www.veritas.com/support/en_US/article.TECH162166

[Marianne]

"Waiting for mount of media id 000007 on server sernb03 for reading." What type of 'reading' are you trying? On which drive type was 000007 written?

[Shoghi]

@D.Flood: All default values, I have never change timeout for any other media server

@Riaan: I wil try this one

@Marianne: This message is from the diagnose option from NB GUI, all tapes are LTO6 on LTO6 drives.

[Marianne]

Please enable Media Manager logging to see why the drive is going DOWN. Add VERBOSE entry to vm.conf on the media server and restart NBU Device Manager. Media Manager events and errors will now be logged in Windows Event Viewer Application and System logs. Next time the drive is DOWN'ed, check Event Viewer logs.

[Shoghi]

@Marianne, I will try this, The error shown in the drive diagnose test option is : Error rewinding the tape but after that it is normaly dismounted, that obvously rewind the tape before unmount.

@Riaan: I have updated the device mapping to verion 1.125 with the same results.

[RiaanBadenhorst]

I would then check your tape device drivers. Maybe something wrong there. Or even the firmware.

[Anonymous]

As well as firmware for drives and library, verify all is looking good from the library as a whole on its own. Check the Error Warning and Trace logs - the easiest way is via the web management front end these libraries have. You can also perform test functions from there. Then proceed to debug NetBackup.

Hopefully still relevant today

https://www-secure.symantec.com/connect/articles/howto-update-tape-library-firmware-minimal-impact-n...

[jim_dalton]

Download, install and use:

LT&T or is that L&TT...I think its the latter library and tape tools.Yes!

This will really give you insight into issues you may have. Invaluable for digging into HP robot/drive issues.

Jim

[Shoghi]

After updating device mapping and reconfiguring devices and media, the library started to work.

Note:

Before upgrade, both LTO5 and LTO6 devices were recognized as HCART3, this library was our first LTo6 device, but after upgrading the device mapping database the LTO5 devices were detected as HCART2, this was a pain because LTO5 tapes were still defined as HCART3, at that point neither LTO5 or LTO6 backups worked, it was necesary to reclasified LTO5 media as HCART2 .

Informational: How to change a volume's media type <- We useed a script for this.

Thanks to all!!!