cancel
Showing results for 
Search instead for 
Did you mean: 

Add tape library & tape drive newly zone to new media server

Rookies
Level 4

Hi Experts,

 

I have zone the existing tape library and tape drive to the new media servers and it is detected from OS level

I run "scan" and here is the result;

C:\Program Files\Veritas\Volmgr\bin>scan

**********************************************************

*********************** SDT_TAPE    **********************

*********************** SDT_CHANGER **********************

**********************************************************

----------------------------------------------------------

Device Name  : ""

Passthru Name: ""

Volume Header: ""

Port: 7; Bus: 0; Target: 0; LUN: 1

Inquiry    : "HP      ESL G3 Series   680H"

Vendor ID  : "HP      "

Product ID : "ESL G3 Series   "

Product Rev: "680H"

Serial Number: "2U33360016_LL0"

WWN          : ""

WWN Id Type  : 0

Device Identifier: "HP      2U33360016_LL0          "

Device Type    : SDT_CHANGER

NetBackup Robot Type: 8

Removable      : Yes

Device Supports: SCSI-3

Number of Drives : 32

Number of Slots  : 702

Number of Media Access Ports: 168

Drive 1 Serial Number      : "82C6E61001"

Drive 2 Serial Number      : "82C6E61007"

Drive 3 Serial Number      : "82C6E6100D"

Drive 4 Serial Number      : "82C6E61013"

Drive 5 Serial Number      : "82C6E61019"

Drive 6 Serial Number      : "82C6E6101F"

Drive 7 Serial Number      : "82C6E61025"

Drive 8 Serial Number      : "82C6E6102B"

Drive 9 Serial Number      : "82C6E61031"

Drive 10 Serial Number      : "82C6E61037"

Drive 11 Serial Number      : "82C6E6103D"

Drive 12 Serial Number      : "82C6E61043"

Drive 13 Serial Number      : "82C6E61091"

Drive 14 Serial Number      : "82C6E61097"

Drive 15 Serial Number      : "82C6E6109D"

Drive 16 Serial Number      : "82C6E610A3"

Drive 17 Serial Number      : "82C6E610A9"

Drive 18 Serial Number      : "82C6E610AF"

Drive 19 Serial Number      : "82C6E610B5"

Drive 20 Serial Number      : "82C6E610BB"

Drive 21 Serial Number      : "82C6E610D9"

Drive 22 Serial Number      : "82C6E610DF"

Drive 23 Serial Number      : "82C6E610E5"

Drive 24 Serial Number      : "82C6E610EB"

Drive 25 Serial Number      : "82C6E610F1"

Drive 26 Serial Number      : "82C6E610F7"

Drive 27 Serial Number      : "82C6E610FD"

Drive 28 Serial Number      : "82C6E61103"

Drive 29 Serial Number      : "82C6E61109"

Drive 30 Serial Number      : "82C6E6110F"

Drive 31 Serial Number      : "82C6E61115"

Drive 32 Serial Number      : "82C6E6111B"

Flags : 0x0

Reason: 0x0

 

I familiar with adding new tape library\drive only through wizard. 

I wanted to add and configure this tape drive via command line. Currently the tape library\drive is configured as shared to the existing media servers.

 

With this command line;

to add robot:

tpconfig -add -robot <robnum> -robtype <robtype> -robpath <devfile>

 

to add tape dirve:

tpconfig -add -drive -type <drvtype> -path <drivepath> -asciiname <asciidrvname> -index <drvindex> -shared [yes|no] -drstatus UP|DOWN|DISABLED [-robot <robnum> -robtype <robtype> -robdrnum <robdrvnum>

 

Based on the information from "scan" command line how can i identify all the value for

<robnum>, <robtype> & <devfile> to add tape library\robot

<drvtype>, <drivepath>, <asciidrvname>, <drvindex>, <robnum>, <robtype> & <robdrvnum> to add new tape drive?

 

Thanks.

 

1 ACCEPTED SOLUTION

Accepted Solutions

revarooo
Level 6
Employee

Why don't you just run: tpautoconf  -a

 

That will discover all devices (tape/robot) and add them in to the NetBackup configuration

If drives are SSO, they will inherit the same drive names.

 

View solution in original post

7 REPLIES 7

SymTerry
Level 6
Employee Accredited

So these are values you have to provide, since you know what hardware you have. This is from the tpconfig documentation (HOWTO43741:( 

-robot robnum

A unique number that identifies the robot to NetBackup. You assign the robot number with the add option.

Robot numbers must be unique for all robots, regardless of the robot type or the host that controls them.

On NetBackup Enterprise Server, robot numbers must be unique for all robots that share the same EMM server (and use the same EMM database). This requirement applies regardless of the robot type or the host that controls them. For example, the same EMM server but different hosts control two TLD robots. If so, the robot numbers must be different.

 

-robtype robtype

Specifies the type of robot that you plan to configure and can be any of the types that NetBackup supports. Check the support Web site to determine the robot type to specify for a particular model of robotic library.

Robot type can be any of the following for NetBackup Enterprise Server:

acs for Automated Cartridge System, tl4 for tape library 4mm, tl8 for tape library 8mm, tld for tape library DLT, tlh for tape library Half-inch, tlm for tape library Multimedia

Robot type can be any of the following for NetBackup server:

tl4 for tape library 4mm

tl8 for tape library 8mm

tld for tape library DLT

 

-robpath devfile

Specifies the robot's device path on the NDMP filer.

On Windows systems, the drive_path variable is a non-NDMP Windows device path for drives. Use it in the {p,b,t,l} format: p is the port, b is the bus, t is the target, and l is the LUN. This information is located in the registry.

Yasuhisa_Ishika
Level 6
Partner Accredited Certified

Currently the tape library\drive is configured as shared to the existing media servers.

This robot have been already configured and controlled on other media server, so use "tpconfig -add -robot robnum -robtype robtype -cntlhost cntlhost" is right option. Provide robot control host and robot number of current configuration.

"tpconfig -add -drive" is option for adding new drive, and not suitable for adding new path to shared drives. Use "tpconfig -add -drpath -path drivepath [-nh ndmp_hostname] [-asciiname asciidrivename] [-drstatus [UP|DOWN|DISABLED]] [-noverify]" instead.

 

 

 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Hopefully 'scan' command showed more than just the output in your post?

In above output the OS sees the robot only, not any tape drives.
The robot is reporting on the tape drives via the robotic control path, but no tape drives are reported at OS level (data path).

Why do you want to use cmd to add devices?
With so many tape drives in one robot, you should have multiple media servers sharing the tape drives or with dedicated drives assigned to each media server.

Trying to correctly configure 32 tape drives manually in a shared/multiple media server environment is asking for trouble/mismatched config.

If you want to use cmd in order to control tape drive names, best to config drive naming rules (info in NBU Admin Guide I) and then use the wizard.

To run the wizard from cmd, use this command:
vmoprcmd -h <media-server-name> -timeout 3600 -autoconfig  -a

revarooo
Level 6
Employee

Why don't you just run: tpautoconf  -a

 

That will discover all devices (tape/robot) and add them in to the NetBackup configuration

If drives are SSO, they will inherit the same drive names.

 

mph999
Level 6
Employee Accredited

Revaroo, yes, I was wondering that ....

 

As a matter of interest, how many drives are you adding to each server ?

I hope it's not all 32 on each media server ???

G_Gate
Not applicable
Partner Certified

Yes Revaroo u r correct.

 

The driver is not compatible or not install at all from the OS level.

Thats why before the media server still unable to see the tape drive after i run this command.

 

Thanks All!

Rookies
Level 4

Thanks GGate. The issue here is because of the driver is not install.

 Thank You Everyone