Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

NBU 7.5 fails to detect tape library

Created: 21 Aug 2012 • Updated: 30 Aug 2012 | 14 comments
This issue has been solved. See solution.

Greetings:

I am doing a new install of NBU 7.5 in a Windows environment using repurposed equipment and it is not detecting the tape library. The Master server and the five media servers are up an running without issue.  Here is the environment:

Master Server: Windows 2008 R2 running on a Dell PowerEdge R900

Media  servers 1 through 4: Windows 2008 R2 on Dell  PowerEdge 2950

Media server for tape library: Windows 2008 on Dell PowerEdge 2850

Tape Library: StorageTek L180 using an Ultra SCSI connection between the library and the media server

All versions of Windows are 64 bit.

Did I miss installing a "driver" for the library or is it a license issue? Or am I heading in the wrong direction?

Thanks.

Comments 14 CommentsJump to latest comment

Will Restore's picture

Check Windows Device Manager.  Can you see the robot and drives?  They must be present at the OS level before Netbackup can configure them.

Will Restore -- where there is a Will there is a way

Marianne's picture

As per Bill's post - forget about NBU.

Verify that OS can see devices.

'Unknown Medium changer' is fine for the robot.

What about tape drive(s)? How are drive(s) connected to server?
What make/model tape drive(s)?

Did you download manufacturer drivers for tape drive(s)?

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

danhatt's picture

Nothing that looks like a tape library in the device manager.

The tape drives will be two StorageTek LTO-4 (HP Ultrium 4), three StorageTek LTO-3 (HP Ultrium 3), two LTO-StorageTek LTO-2 (IBM Ultrium-TD2).

I'm not planning on using the LTO-2 drives, but have been instructed to install them "just in case".

Drives arev Fibre Channel going through a Brocade switch.  I am waiting for the admin name a password to get the drives connected.  I did do  trial run and it appears the drives can be detected by NBU. No new drivers at this point.

mph999's picture

You need to get the library visible in  windows device manager, until that happens, NBU will never see it.

I would image the most likely reason it is not there is zoning, excuse me if  am wrong.

The library documentation should assist with this if you are having trouble.

Martin

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805
 
Marianne's picture

You need to verify robot -> host connection.

Troubleshoot one at a time - if SCSI connection, verify that robot interface connects to correct SCSI card on media server. for example - if HVD robotic interface on L180, you cannot connect it to a LVD SCSI card.

Always best to download and install correct manufacturer tape drivers - HP drivers from HP support site, IBM tape drivers from IBM web site.

Please verify that robot and tape drives are seen in Device Manager before any attempts to config them in NBU.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

SOLUTION
danhatt's picture

Thanks for the suggestions.

Marianne: I think it is a SCSI issue as you referred to. 

I can document that the SCSI cards available are LVD via their web sites. However, as best I can make out, the StorageTek L180 uses a HVD SCSI connection. One web page indicated you could get LVD SCSI, but only at an extra cost. I have no documentation for the tape library except what I can find on-line.  I am rumored to be the fifth admin using this library and only one is still around.

All: Does anyone have any ideas/suggestions on determining what SCSI type is on the library.

My next step is to see if the controller can be seen via an IP address or if that is only for remoting in using (at an extra cost) software.

DAN

Marianne's picture

I have worked for STK resellers for about 12 years - every single L180 that we sold had HVD interface. They are good, solid libraries with little or no 'issues'. Like with any mechanical device, you need to have a  maintenance contract with a support partner. Their technical staff will help you to get the robot up and running in no time.

PLEASE do not connect HVD device to LVD hba:
HVD = HIGH voltage differential
LVD = Low voltage differential

Easiest will be to purchase HVD hba.

I have Googled images for HVD, LVD, and SE. Hopefully this link will work:

http://www.computeranddata.com/doc/notes/SCSI-specs_files/_technology_scsi_files/technology_scsi-icons.gif

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

danhatt's picture

Marianne: Thank you ever so much.  The images were extremely helpful and made very short work of determining that we did not have the right type of SCSI card on the media server.

I have been given the go ahead to purchase a new SCSI card that will work in either a Dell PowerEdge R900 or a Dell PowerEdge 2850. However, all I am finding are used cards and the organization I work for cannot purchase these.

I've also seen LVD/HVD converters.  Has anyone used one of these? What has been your experience with them?

Thanks.

DAN

Nicolai's picture

I would recommend to skip the SCSI fuss and FC enable the L180.

Option 1: YXSL180-1GB-FC this is a upgrade kit that will equip the L180 with a 1GB FC interface. Cost from new is approximately 2500USD including installation cost. There are many company that sell those cards second hand.

Option 2: Use a SCSI to FC router. Like this one http://www.tech.proact.co.uk/storagetek/storagetek_storagenet_sn3250_fibre_channel_router.htm Rock stable box - switch it on and forget it. The router does full 1GB routing.

Oracle mentiones two types of converts, see 6.3 : http://docs.oracle.com/cd/E19828-01/MT9112N/MT9112N.pdf

I personally never used HVD->LVD converters. Any convert could potential limit transfer speed. But since this is the robot interface we can disregard this concern. FC enabling the robot will allow you to place the robot outside the data center - maybe in a another building. Placing orginal and backup data is general not consider to be a best practice. 

Assumption is the mother of all mess ups.

If this post answered your'e qustion -  Please mark as a soloution.

danhatt's picture

Thanks, Nicolai, for the information. Unfortunately neither option is viable where I work. The upgrade kit does not appear to be available as new and there is a policy of not purchasing used equipment. The SCSI router is too expensive. 

We have decided to go with a SCSI card that fits the Dell R900 and a converter between it and the L180 Tape library.  This is contingent on finding the converter (Paralon MH32A) at a seller we have a contract with.

Thank you everyone for the help. If I am able to get the converter I will let you know how it worked out.

Nicolai's picture

Good luck with the project. 

Have you considered to search for exemption regarding the policy of not purchasing used equipment. I would say you have some very good arguments. By re-using a L180 you are saving the company a lot of money - But give the age of the L180 you are forced to buy second parts. Just get quote of a new robot and let the manger compare the 1000 if difference :-D 

Best Regards

Nicolai

Assumption is the mother of all mess ups.

If this post answered your'e qustion -  Please mark as a soloution.

Will Restore's picture

L180 is what, 10 to 12 years old, can you even get support any more other than used parts?

Will Restore -- where there is a Will there is a way

danhatt's picture

I work for the government. Capital purchases take years to get approved and then actually purchased. System is very strict and there is no easy way to get around it.  If it was private industry it would be a different matter.

Thanks.

danhatt's picture

Thanks to everyone. All of the information was either useful in determining the original problem or gave me information to take to management as to why it would not work.