Video Screencast Help

tape drives in SSO

Created: 02 Oct 2012 • Updated: 03 Oct 2012 | 13 comments
This issue has been solved. See solution.

Hi ALL,

 

I have my tape drives in SSO mode.It is shared.

 

Will my SCSI cable be connected between server and library in this case?

Comments 13 CommentsJump to latest comment

CRZ's picture

Do you REALLY have tape drives or is this a "just suppose" situation?

Are you also NIKHIL2346565959?

Arun K's picture

No I am not.Why everybody is calling me with that name.

 

Yes i have a tape drive.

CRZ's picture

Well, to be blunt, it's because we had to ask about a dozen times before you finally answered the question instead of ignoring it.

The library will have to be connected to the server SOMEHOW.  Is that SCSI?  Is it fibre?  I cannot say.

There's a nice diagram on page 293 of the 7.1 Troubleshooting Guide of a basic SSO environment which may or may not help you figure it out:

Symantec NetBackup 7.1 Troubleshooting Guide
 http://symantec.com/docs/DOC3683

 

There's also a nice diagram on page 138 of the Shared Storage Guide:

Symantec NetBackup 7.1 Shared Storage Guide
 http://symantec.com/docs/DOC3659

Hope this documentation helps you research this answer!

Arun K's picture

Does library also have a SCSI card or HBA card?

CraigV's picture

I mistakenly posted here when I saw the original question thinking it was BE's SAN SSO which DOESN'T work with a SAS/SCSI drive...hence the name SAN Shared Storage Option. I am not sure if NBU does the same thing...I ended up deleting my post, but not the subscription so these questions have been coming up.

If you don't know the difference between a SCSI card or HBA and whether or not they get installed into a tape library (they don't!!! surprise) or into a server (they DO!!! wink) then I'd suggest trying to get NBU working and do an A+ certification where you will learn the basics of hardware. I don't mean to be nasty, but was that a real question?

Libraries have tape drives in them with interface cards. Not HBAs. These interface cards are then connected to a fibre channel switch, or server's SCSI/SAS card. Lesson over...

THanks!

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

Arun K's picture

I have 10 tape drives in my Library and they are zoned .So each tape drive will have a HBA?

Stuart Green's picture

crying

http://www.youtube.com/watch?v=l7-6m2cE6JM

Tip: Get overview/document your NBU environment. Run 'nbsu' and review the output.

• If this provides help, please vote or mark appropriate solution.

mph999's picture

OK, HBAs are only found in servers, as are scsi cards.

Generally, well on the libraries I used to get to play with the fibre cable ran from the drive to the patch panel on the library, and from there to the switch.  So no, each drive does not have an HBA at the library side.

From the switch, cables run to the HBAs, one cable per port on the HBA.

Keeping it simple, if you have x4 drives, and 1 HBA card with x2 ports, it is the SAN zoning that controls which drive is 'connected' to which port, so you would 'zone' drives 1 and 2 to port 1 on the HBA and drives 3 and 4 to port 2 on the HBA.

It is a bit more complex, and one thing you have to calculate is how many drives each port on the HBA can support.  The HBA only has X amount of bandwidth, and so the total bandwidth required of the drives (running at full speed) connected to a single port on a HBA must not exceed the capabilities of the port.

I'm too tired to do the maths right this second, but if I remember correctly, if you had a single 2Gb HBA, you could only attach 1 or 2 LTO5 drives.  If you connect say 4, and ran all the drives at the same time, the HBA  could not support the bandwidth required, and the drives would never run at full speed.

I don't really understand this question:

"Will my SCSI cable be connected between server and library in this case?"

Where did you think it would be connected ?

There is nothing particularly special about SSO (ok, it gets a biit complex when you have to troubleshoot it) but all it means, is that a single tape drive can be connected to multiple servers, and this is all done via zoning.  There is still on one cable from the drive to the switch , and from the a cable from the switch to each of the servers, but what serevrs and see which tape drives is all controlled by zoning.

 

Martin

 

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

that's unique number for HBA unlike LAN card has MAC address

 Cheers !!!

CJS

 

Marianne's picture

Please Arun - you don't have NBU questions.

You have already received more than enough advice to get basic SAN training elsewhere.
Have you gone through ANY of the URLs suggested in previous posts?

You can even Google 'SAN basics'. LOTS of very useful info, e.g. 
http://storageareanetwork.starwindsoftware.com/
http://en.wikipedia.org/wiki/Storage_area_network

Next, Google 'SAN zoning basics'.

If you have a REAL environment, find out who is managing your SAN. Ask him to show you the switch and how all is connected to devices and servers. Also where WWN fits into the picture...
Then read through section 2 of the SSO manual - see link in CRZ's post.

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

Arun K's picture

Windows:

C:\VERITAS\Volmgr\bin>scan
************************************************************
*********************** SDT_TAPE    ************************
*********************** SDT_CHANGER ************************
*********************** SDT_OPTICAL ************************
************************************************************
------------------------------------------------------------
Device Name  : "Tape2"
Passthru Name: "Tape2"
Volume Header: ""
Port: 0; Bus: 0; Target: 1; LUN: 1
Inquiry    : "IBM     ULTRIUM-TD4      "
Vendor ID  : "IBM     "
Product ID : "ULTRIUM-TD4     "
Product Rev: " "
Serial Number: 0
WWN          : ""
WWN Id Type  : 0
Device Identifier: "IBM     ULTRIUM-TD4     0
Device Type    : SDT_TAPE
NetBackup Drive Type: 3
Removable      : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name  : "Tape3"
Passthru Name: "Tape3"
Volume Header: ""
Port: 0; Bus: 0; Target: 1; LUN: 2
Inquiry    : "IBM     ULTRIUM-TD4      "
Vendor ID  : "IBM     "
Product ID : "ULTRIUM-TD4     "
Product Rev: " "
Serial Number: 0
WWN          : ""
WWN Id Type  : 0
Device Identifier: "IBM     ULTRIUM-TD4     0
Device Type    : SDT_TAPE
NetBackup Drive Type: 3
Removable      : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name  : "Tape4"
Passthru Name: "Tape4"
Volume Header: ""
Port: 1; Bus: 0; Target: 0; LUN: 1
Inquiry    : "IBM     ULTRIUM-TD4      "
Vendor ID  : "IBM     "
Product ID : "ULTRIUM-TD4     "
Product Rev: " "
Serial Number: 0
WWN          : ""
WWN Id Type  : 0
Device Identifier: "IBM     ULTRIUM-TD4     0
Device Type    : SDT_TAPE
NetBackup Drive Type: 3
Removable      : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
 

unix:

root@media01:~>scan -changer
************************************************************
*********************** SDT_CHANGER ************************
************************************************************
------------------------------------------------------------
Device Name  : "/dev/sg11"
Passthru Name: "/dev/sg11"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : "IBM     03584L32        7420"
Vendor ID  : "IBM     "
Product ID : "03584L32        "
Product Rev: "7420"
Serial Number: "0000000232890401"
WWN          : ""
WWN Id Type  : 0
Device Identifier: "IBM     03584L32        0000000232890401"
Device Type    : SDT_CHANGER
NetBackup Robot Type: 8
Removable      : Yes
Device Supports: SCSI-3
Number of Drives : 3
Number of Slots  : 500
Number of Media Access Ports: 32
Drive 1 Serial Number      : "0007867128"
Drive 2 Serial Number      : "0007858969"
Drive 3 Serial Number      : "0007867217"
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name  : "/dev/sg9"
Passthru Name: "/dev/sg9"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : "IBM     03584L32        7420"
Vendor ID  : "IBM     "
Product ID : "03584L32        "
Product Rev: "7420"
Serial Number: "0000000232890401"
WWN          : ""
WWN Id Type  : 0
Device Identifier: "IBM     03584L32        0000000232890401"
Device Type    : SDT_CHANGER
NetBackup Robot Type: 8
Removable      : Yes
Device Supports: SCSI-3
Number of Drives : 3
Number of Slots  : 500
Number of Media Access Ports: 32
Drive 1 Serial Number      : "0007867128"
Drive 2 Serial Number      : "0007858969"
Drive 3 Serial Number      : "0007867217"
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name  : "/dev/sg7"
Passthru Name: "/dev/sg7"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : "IBM     03584L32        7420"
Vendor ID  : "IBM     "
Product ID : "03584L32        "
Product Rev: "7420"
Serial Number: "0000000232890401"
WWN          : ""
WWN Id Type  : 0
Device Identifier: "IBM     03584L32        0000000232890401"
Device Type    : SDT_CHANGER
NetBackup Robot Type: 8
Removable      : Yes
Device Supports: SCSI-3
Number of Drives : 3
Number of Slots  : 500
Number of Media Access Ports: 32
Drive 1 Serial Number      : "0007867128"
Drive 2 Serial Number      : "0007858969"
Drive 3 Serial Number      : "0007867217"
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name  : "/dev/sg5"
Passthru Name: "/dev/sg5"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : "IBM     03584L32        7420"
Vendor ID  : "IBM     "
Product ID : "03584L32        "
Product Rev: "7420"
Serial Number: "0000000232890401"
WWN          : ""
WWN Id Type  : 0
Device Identifier: "IBM     03584L32        0000000232890401"
Device Type    : SDT_CHANGER
NetBackup Robot Type: 8
Removable      : Yes
Device Supports: SCSI-3
Number of Drives : 3
Number of Slots  : 500
Number of Media Access Ports: 32
Drive 1 Serial Number      : "0007867128"
Drive 2 Serial Number      : "0007858969"
Drive 3 Serial Number      : "0007867217"
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name  : "/dev/sg3"
Passthru Name: "/dev/sg3"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : "IBM     03584L32        7420"
Vendor ID  : "IBM     "
Product ID : "03584L32        "
Product Rev: "7420"
Serial Number: "0000000232890401"
WWN          : ""
WWN Id Type  : 0
Device Identifier: "IBM     03584L32        0000000232890401"
Device Type    : SDT_CHANGER
NetBackup Robot Type: 8
Removable      : Yes
Device Supports: SCSI-3
Number of Drives : 3
Number of Slots  : 500
Number of Media Access Ports: 32
Drive 1 Serial Number      : "0007867128"
Drive 2 Serial Number      : "0007858969"
Drive 3 Serial Number      : "0007867217"
Flags : 0x0
Reason: 0x0
------------------------------------------------------------
Device Name  : "/dev/sg1"
Passthru Name: "/dev/sg1"
Volume Header: ""
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry    : "IBM     03584L32        7420"
Vendor ID  : "IBM     "
Product ID : "03584L32        "
Product Rev: "7420"
Serial Number: "0000000232890401"
WWN          : ""
WWN Id Type  : 0
Device Identifier: "IBM     03584L32        0000000232890401"
Device Type    : SDT_CHANGER
NetBackup Robot Type: 8
Removable      : Yes
Device Supports: SCSI-3
Number of Drives : 3
Number of Slots  : 500
Number of Media Access Ports: 32
Drive 1 Serial Number      : "0007867128"
Drive 2 Serial Number      : "0007858969"
Drive 3 Serial Number      : "0007867217"
Flags : 0x0
Reason: 0x0
root@media01:~>

Although in netbackup we can only specify 1 sg instance (only 1 device) for each library control...
In netbackup volmgr database we can configure failover multipath for tape devices, but we can´t configure the same for robotic path's:

root@media01:~>tpconfig -d
Id  DriveName           Type   Residence
      Drive Path                                                       Status
****************************************************************************
0   TS3500.LTO4.DRV02... hcart  TLD(2)  DRIVE=2
      /dev/nst5                                                        UP
      /dev/nst0                                                        UP
1   TS3500.LTO4.DRV03... hcart  TLD(2)  DRIVE=3
      /dev/nst4                                                        UP
      /dev/nst2                                                        UP
2   TS3500.LTO4.DRV01... hcart  TLD(2)  DRIVE=1
      /dev/nst3                                                        UP
      /dev/nst1                                                        UP

Currently defined robotics are:
  TLD(2)     robotic path = /dev/sg1

EMM Server = mstr1

 

What is the WWN here for tape drives?

in case of windows and unix?

Difference between serial number and WWN?

Drive has WWN or serial number?

Marianne's picture

Speak to your SAN administrator - what is the purpose of SIX paths to the library???

About multipathing for robots, see this: http://www.symantec.com/docs/TECH60395

 

What is the WWN here for tape drives?
Device Inquiry string does not display WWN. As you can see - the field is empty.
SAN Administrators will use third-party tools to see WWN.

in case of windows and unix?
Run the command on both and see for yourself.

Difference between serial number and WWN?
NBU uses serial number to determine unique device and map to different media servers. (See SSO manual)
WWN is used by your SAN admin for zoning.

Drive has WWN or serial number?
both.

 

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

SOLUTION