cancel
Showing results for 
Search instead for 
Did you mean: 

failed to configure DD tape library (VTL ) in netbackup

Raaavan
Level 5

Dear All,

We are failed to configure DD tape library in netbackup below are the details

DD is published & configured as VTL tape library on master server & it also a robotic host for the same

the same tape drives are zoned to one of media server named as hydt5440-nbmed1 but here i could not configure this library either through wizard or command line

Wizard error

Unable to determine robot type.
Drive is standalone or in unknown robot.
The robot drive number for this drive is unknown.

tpcommand logs are attached with verbosity 5

What i came to know about zoning w.r.t. DD as VTL is only changer is enough to publish all tape drives on destination server. no need to zone robotic path as it used to be in physical tape library
Still confused about this theory on DD
 

Currently everything is   working on master which is robotic host please suggest 

Master serer - Solaris / 7.5.0.6 ( robotic host for that VTL library )
Media serer -  Solaris / 7.5.0.6 

devfsadm sgbuild & everything is performed on media serer 

 

 

 

1 ACCEPTED SOLUTION

Accepted Solutions

mph999
Level 6
Employee Accredited

On the + side, scan works so in theory, NBU will configure drives now via the device wizard (be sure to select both the media serevr vand the robot control host at the same time).

On the negative side, 102 tape drives will be interesting ...  Things might not even work correctly with that number.

That will put an unnecessary load on N NBU (it has to monitor all these drives) and as Revaroo says, you can't use 102 drives at once, max should be around 10 (though you can probably only write to less than that at the same time at full speed, due to the limits of the OS/ H/ware of the media server).

View solution in original post

7 REPLIES 7

Marianne
Level 6
Partner    VIP    Accredited Certified
NBU can only add what is presented via the OS and according to what is returned by the hardware via scsi_command. Have you checked the NBU Hardware Compatibility guide for this make/model? And the configuration notes in the VTL section? Please run 'scan ' command from cmd in volmgr/bin folder and post output.

mph999
Level 6
Employee Accredited

The robot should only be seen by one server, that being the server you want to be the robot control host.  Typically the master is used.

So the master will see the robot and the tape drives.

The media server only needs to see the tape drives.

As Marianne says, the OS HAS to correctly report the devices before NBU can configure or use them.

So, you can check what the OS sees with cfgadm -al -o show_FCP_dev command

(sometimes you have to use a different command, but this usually works).

Once the OS can see the devices, test that they display correctly with scan command.  You may have to rebuild the sg drivers on solaris:

cd /usr/openv/volmgr/bin/driver

cp sg.conf sg.conf.old

cp sg.links sg.links.old

../sg.build all

#!/usr/bin/ksh

modunload -i $(echo $(modinfo |grep "sg (SCSA" |awk '{print $1}'))
mv /kernel/drv/sg.conf /kernel/drv/sg.conf.old
/usr/openv/volmgr/bin/driver/sg.install


Martin

 

 

Raaavan
Level 5

devfsadm followed by sg.build is already done please find attached scan & cfgadm output

DD wnn are marked in cfgadm output


 

revarooo
Level 6
Employee

why have you zoned so many drives (102)? Do you expect to use them all at the same time?

You won't be able to!

you shouldn't need more than 10 drives zoned to one media server as you will not be able to stream data to them efficiently all at the same time with 102 (LOL)

 

 

mph999
Level 6
Employee Accredited

On the + side, scan works so in theory, NBU will configure drives now via the device wizard (be sure to select both the media serevr vand the robot control host at the same time).

On the negative side, 102 tape drives will be interesting ...  Things might not even work correctly with that number.

That will put an unnecessary load on N NBU (it has to monitor all these drives) and as Revaroo says, you can't use 102 drives at once, max should be around 10 (though you can probably only write to less than that at the same time at full speed, due to the limits of the OS/ H/ware of the media server).

Raaavan
Level 5

Server having 128 GB RAM with latest M9K series & mainly used for tier 1 backups
I am also concern about maximum no of lun's already asked OS team to release unwanted devices mapped to HBA port
Lets see how it goes



Pos  Port_ID Hard_Addr Port WWN         Node WWN         Type
0    12f00   0         5005076802406066 5005076802006066 0x0  (Disk device)
1    13e00   0         5005076802406067 5005076802006067 0x0  (Disk device)
2    14a00   0         5005076802407496 5005076802007496 0x0  (Disk device)
3    15a00   0         5005076802407497 5005076802007497 0x0  (Disk device)
4    1a700   0         50060e8010463801 50060e8010463801 Failed to get the type.
5    1f280   0         500601613ce027b0 50060160bce027b0 0x0  (Disk device)
6    1f580   0         5006016a3ce027b0 50060160bce027b0 0x0  (Disk device)
7    1bb00   0         10000000c9b09b34 20000000c9b09b34 0x1f (Unknown Type,Host Bus Adapter)

Pos  Port_ID Hard_Addr Port WWN         Node WWN         Type
0    10400   0         500507630f791307 500507630f391307 0x1  (Tape device)
1    10500   0         500507630f791308 500507630f391308 0x1  (Tape device)
2    10600   0         500507630f791309 500507630f391309 0x1  (Tape device)
3    10700   107ba     500507630f79130a 500507630f39130a 0x1  (Tape device)
4    10800   0         500507630f79130b 500507630f39130b 0x1  (Tape device)
5    10900   109c6     500507604441ed06 500507604401ed06 0x1  (Tape device)
6    10a00   0         500507604441ed07 500507604401ed07 0x1  (Tape device)
7    10b00   0         500507604441ed08 500507604401ed08 0x1  (Tape device)
8    10c00   0         500507604441ed09 500507604401ed09 0x1  (Tape device)
9    10d00   0         500507604441ed0a 500507604401ed0a 0x1  (Tape device)
10   11300   0         10000000c9b09b35 20000000c9b09b35 0x1f (Unknown Type,Host Bus Adapter)

Pos  Port_ID Hard_Addr Port WWN         Node WWN         Type
0    12900   0         2a10002188a7dae1 2000002188a7dae1 0x8  (Medium changer device)
1    11200   0         10000000c99536fc 20000000c99536fc 0x1f (Unknown Type,Host Bus Adapter)


Pos  Port_ID Hard_Addr Port WWN         Node WWN         Type
0    12f00   0         5005076802306066 5005076802006066 0x0  (Disk device)
1    13e00   0         5005076802306067 5005076802006067 0x0  (Disk device)
2    14a00   0         5005076802307496 5005076802007496 0x0  (Disk device)
3    15a00   0         5005076802307497 5005076802007497 0x0  (Disk device)
4    1b700   0         50060e8010463803 50060e8010463803 Failed to get the type.
5    1f280   0         5006016b3ce027b0 50060160bce027b0 0x0  (Disk device)
6    1f580   0         500601623ce027b0 50060160bce027b0 0x0  (Disk device)
7    1bb00   0         10000000c99536fd 20000000c99536fd 0x1f (Unknown Type,Host Bus Adapter)


Pos  Port_ID Hard_Addr Port WWN         Node WWN         Type
0    10400   0         500507630f79130c 500507630f39130c 0x1  (Tape device)
1    10600   0         500507630f791312 500507630f391312 0x1  (Tape device)
2    10700   0         500507630f791313 500507630f391313 0x1  (Tape device)
3    10900   0         500507630f791316 500507630f391316 0x1  (Tape device)
4    10a00   10ab1     500507604441ed11 500507604401ed11 0x1  (Tape device)
5    10b00   0         500507604441ed12 500507604401ed12 0x1  (Tape device)
6    10c00   0         500507604441ed13 500507604401ed13 0x1  (Tape device)
7    10d00   0         500507604441ed14 500507604401ed14 0x1  (Tape device)
8    10e00   10eab     500507604441ed15 500507604401ed15 0x1  (Tape device)
9    11300   0         10000000c9b09e2c 20000000c9b09e2c 0x1f (Unknown Type,Host Bus Adapter)


Pos  Port_ID Hard_Addr Port WWN         Node WWN         Type
0    10e00   0         26000021884c57ef 20000021884c57ef 0x8  (Medium changer device)
1    11700   0         2100001b3207e996 2000001b3207e996 0x1f (Unknown Type,Host Bus Adapter)

Pos  Port_ID Hard_Addr Port WWN         Node WWN         Type
0    10400   0         500507630f791301 500507630f391301 0x1  (Tape device)
1    10500   0         500507630f791302 500507630f391302 0x1  (Tape device)
2    10600   0         500507630f791304 500507630f391304 0x1  (Tape device)
3    10800   0         500507630f791306 500507630f391306 0x1  (Tape device)
4    10900   109cc     500507604441ed01 500507604401ed01 0x1  (Tape device)
5    10a00   10acb     500507604441ed02 500507604401ed02 0x1  (Tape device)
6    10b00   10bca     500507604441ed03 500507604401ed03 0x1  (Tape device)
7    10c00   0         500507604441ed04 500507604401ed04 0x1  (Tape device)
8    10d00   10dc7     500507604441ed05 500507604401ed05 0x1  (Tape device)
9    11800   0         2101001b3227e996 2001001b3227e996 0x1f (Unknown Type,Host Bus Adapter)

Pos  Port_ID Hard_Addr Port WWN         Node WWN         Type
0    10400   0         500507630f791317 500507630f391317 0x1  (Tape device)
1    10500   105a7     500507630f791318 500507630f391318 0x1  (Tape device)
2    10600   0         500507630f791319 500507630f391319 0x1  (Tape device)
3    10800   0         500507630f79131b 500507630f39131b 0x1  (Tape device)
4    10900   0         500507630f79131c 500507630f39131c 0x1  (Tape device)
5    10a00   0         500507604441ed16 500507604401ed16 0x1  (Tape device)
6    10b00   0         500507604441ed19 500507604401ed19 0x1  (Tape device)
7    10c00   0         500507604441ed1a 500507604401ed1a 0x1  (Tape device)
8    10d00   10da3     500507604441ed1b 500507604401ed1b 0x1  (Tape device)
9    10e00   10e9f     500507604441ed1c 500507604401ed1c 0x1  (Tape device)
10   11600   0         2101001b32b5c32b 2001001b32b5c32b 0x1f (Unknown Type,Host Bus Adapter)

 

 

VoropaevPavel
Level 4
Partner Accredited

I've noticed that some of them support SCSI-6 and others are SCSI-3 are those from the same library?