Video Screencast Help

1 robot with 2 drives - seems in netbackup like 2 robots with 2 drives

Created: 05 Jul 2010 • Updated: 10 Aug 2012 | 7 comments
This issue has been solved. See solution.

Hi all
Before explain my problem - sorry for my english , maybe i cant explain correctly but  try to do it
Firstly explain situation
I have Netbackup 6.0  on Master server and there was robot FS ,  with 2 drives .  after  robot was broken , company  bought  new HP robot with 2 drives ,  i delete all settings depending old robot  ( except policy ,storage unit and etc  that i have )  and try to add new robot
the topology of my network is like - i connect  robot with 2 fiber  to different 2 switches ( per 1 fiber to each switch ) , Netbackup Master server also connected via 2 fiber to both 2 switches ( per 1 fiber to each switches) , all other media server also connected via 2 fiber to each switches   ( i know   structure is  complicated , but i receive infrastructure like this from previous backup admin) 
problem is HP robot that i connect to  netbackup1 master server i see like 2 robot and 2 drive

 /usr/openv/volmgr/bin/tpautoconf -report_disc

======================= New Device (Robot) =======================
 Inquiry = "HP      MSL G3 Series   7.00"
 Serial Number = **********_LL1
 Robot Path = /dev/sg3
 Number of Drives = 1
 Number of Slots = 24
 Number of Media Access Ports = 0
 Drive = 1, Drive Name = /dev/nst1, Serial Number = ********HR
======================= New Device (Drive) =======================
 Inquiry = "HP      Ultrium 4-SCSI  H58W"
 Serial Number = ********HR
 Drive Path = /dev/nst1
 Found as drive=1 in new robot
   Robot's inquiry = "HP      MSL G3 Series   7.00"
   Robot's Serial Number = **********_LL1
   Robot's device path = /dev/sg3
======================= New Device (Drive) =======================
 Inquiry = "HP      Ultrium 4-SCSI  H58W"
 Serial Number = ********HE
 Drive Path = /dev/nst0
 Found as drive=1 in new robot
   Robot's inquiry = "HP      MSL G3 Series   7.00"
   Robot's Serial Number = **********_LL0
   Robot's device path = /dev/sg1
======================= New Device (Robot) =======================
 Inquiry = "HP      MSL G3 Series   7.00"
 Serial Number = **********_LL0
 Robot Path = /dev/sg1
 Number of Drives = 1
 Number of Slots = 24
 Number of Media Access Ports = 0
 Drive = 1, Drive Name = /dev/nst0, Serial Number = ********HE

--------------------
As you see from tpautoconfig it see robot like - 2 robot.. if i try to add from  netbackup interface  - when i try to add master  server it  show me 2 robot..  2 drives (  i cant drag and drop the drive from one robot to another) - final problem is
When i try to add media - it see per robot - 1 drive with 24 tapes
I Need 1 Robot  with 2 drives = 48 tapes ( as was before with FS robot)
if i try to add it manually via tpconfig menu (  first add robot, then add  each driver )  - i have other situation after adding  , i have  1 robot via   netbackup interface and two drives - but when i try to add media   in only one robot i see only 24 tapes ( not 48 )

who meet the problem like this, please advice me ( i  tired to make  hundred of changes - but no result ,
thanks in advance
 

Comments 7 CommentsJump to latest comment

Ed Wilts's picture

Unlike disk drives, tape drives and robots do not support multipathing.  You can connect your robot to only switch at a time.

You can put 1 tape drive on one switch and the 2nd tape drive on the 2nd switch, but the robot itself should be on only 1 switch.

If this post helps you, please add a vote.

If this post answers your question, please mark it as a solution.  Thanks!
 

Marianne's picture

Robotic multipathing supported as from NBU 6.5.2:

ftp://exftpp.symantec.com/pub/support/products/Net...

Highly Available Tape Libraries Enabling Multiple Robotic Paths

NetBackup 6.0 became the first release to support multiple paths to tape drives.
....
NetBackup 6.5.2 is the first release to support multiple paths for robots or tape libraries.

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

Ed Wilts's picture

Thanks for the info Marianne, but he's still running 6.0 which you pointed out does not support mutiple paths for robots.  So for now, I think his best bet is to single-path the robot until he can upgrade to at least 6.5.2.

If this post helps you, please add a vote.

If this post answers your question, please mark it as a solution.  Thanks!
 

xiazhen's picture

hi, the guys:

     under the circumstance , you can enable the cofigure of operation system .

you can reconfigure the device in nbu. it will be display a robotic.

best regards

xiazhen

demo4119's picture

Configure as single path for time being might solve the problem .
Till customer upgrade the NBU .

SOLUTION
Stuart Green's picture

Agree with configuring single paths - so remove 1 fibre from each drive and configure from there. At least get the backup devices working. Then delve into multipathing if you do need to use it.

(I have a MSL G3 series and only have 1 fibre connection on my drives - but do have 2 libraries running - 1 in primary and 1 in secondary site)

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

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

Rick Brown's picture

Is it possible the drives are hosting the robotic control paths and these features are turned on for both drives?
IBM's 1120's host robotic control pathing through the drives. If you have 20 tape drives, it is possible to configure 20 robotic paths, 1 through each tape drive.
We use 2 robotic paths for each logical partition (for failover) & it works very well. We had to create 2 robotic definition files for the host server. Whe we configure drive, we see 2 robots, and a bunch of drives (the master server is the robotic control host).

I don't see where this is a problem - having 2 robotic paths. NBU will use 1 unless it goes down, & the other path should handle the robotic tasks if the primary goes down.