autoloader(robot) and tape drive configuration using command line

[raviteja_yedlap]

Hi,

I need to do automated procedure using command line for autoloader and tape drive configuration, for that i have used /usr/openv/volmgr/bin/tpautoconf -a instead of doing manually in Netbackup GUI(media and device management).I am sucessfully able to list robots and tape drives,but not able to create storage unit automatically.Do i need to create storage unit manually. storage units are getting created automatically if do above procedure using media and device management(divice wizard) using Netbackup GUI .

[root@ xxxxxxxx  bin]# /usr/openv/volmgr/bin/tpconfig -l
Device Robot Drive       Robot                    Drive                 Device     Second
Type     Num Index  Type DrNum Status  Comment    Name                  Path       Device Path
robot      0    -    TLD    -       -  -          -                     /dev/sg23
  drive    -    0 hcart3    2      UP  -          HP.ULTRIUM6-SCSI.000  /dev/nst7
  drive    -    0 hcart3    2      UP  -          HP.ULTRIUM6-SCSI.000  /dev/nst4
  drive    -    0 hcart3    2      UP  -          HP.ULTRIUM6-SCSI.000  /dev/nst3
  drive    -    0 hcart3    2      UP  -          HP.ULTRIUM6-SCSI.000  /dev/nst1
  drive    -    1 hcart3    1      UP  -          HP.ULTRIUM6-SCSI.001  /dev/nst6
  drive    -    1 hcart3    1      UP  -          HP.ULTRIUM6-SCSI.001  /dev/nst5
  drive    -    1 hcart3    1      UP  -          HP.ULTRIUM6-SCSI.001  /dev/nst2
  drive    -    1 hcart3    1      UP  -          HP.ULTRIUM6-SCSI.001  /dev/nst0

[root@ xxxxxxxx bin]# /usr/openv/netbackup/bin/admincmd/bpstulist

[root@xxxxxxxx bin]

Please help me in resolving this.

Regards,

Raviteja

[RiaanBadenhorst]

Hello

I'm all for automating repetitive tasks, but why would you automate device configuration. It surely doesn't occur that often, does it?

Anyways, you can use bpstuadd to create the storage unit.

C:\Program Files\Veritas\NetBackup\db\error>bpstuadd -?
bpstuadd: unrecognized option -?
USAGE: bpstuadd -label storage_unit_label [-verbose]
                    -path path_name [-dt disk_type]
                        or
                    -dp disk_pool [-dt disk_type]
                        or
                    -density density_type [-rt robot_type -rn robot_number]
                    [-host host_name]
                    [-cj max_jobs]
                    [-odo on_demand_only_flag]
                    [-mfs max_fragment_size]
                    [-maxmpx mpx_factor]
                    [-nh NDMP_attach_host]
                    [-tt transfer_throttle]
                    [-nodevhost]
                    [-flags flags]
                    [-cf clearfiles]
                    [-hwm high_water_mark]
                    [-lwm low_water_mark]
                    [-okrt ok_on_root]
                    [-hostlist host_name [host_name]
                    [-M master_server[,master_server]
                    [-reason "<reason>"]
                        or
       bpstuadd -group storage_unit_group storage_unit_label [storage_unit_label]
                    [-sm selection_method]

          Valid values for selection_method:
               Prioritized = 1 (DEFAULT)
               Least Recently Selected = 2
               Failover = 3
               Media Server Load Balance = 4
            Only valid for storage unit groups
          Valid values for dp: Disk Pool Must Already Exist
            Only valid for DiskPool type disk storage units
          Valid values for hostlist:
            Only valid for DiskPool type disk storage units
          Valid values for max_jobs: 0..4096
          Valid values for mpx_factor: 1..32
          Valid values for on_demand_only_flag: 0 or 1
          Valid values for disk_type:
              Basic = 1 (-path DEFAULT)
              NearStore = 2
              SnapVault = 3
              DiskPool = 6 (-dp DEFAULT)
          Valid values for flags: NONE or STAGE_DATA
          Valid values for cf: 0, 1, or 2 (2 if supported by specified storage server)
            Only valid for disk storage units
          Valid values for transfer_throttle: 0..9999999
          Valid values for high_water_mark: 1..100 percentage
            Only valid for disk storage units (Except DiskPool and SnapVault)
          Valid values for low_water_mark: 0..99 percentage
            Only valid for disk staging storage units (Except DiskPool and SnapVault)
          Valid values for ok_on_root: 0 or 1
            Only valid for Basic disk storage units
          max_fragment_size in MB:
            For removable media, either between 50 and 1048576 (1024GB) or 0.
              0 is equivalent to the largest allowed value, 1048576.
            For disk, between 20 and 524288 (512GB)

          NOTICE for Pre 6.0 Media Servers:
            (-tt, -hwm, -lwm, -okrt) Options are IGNORED and Set APPROPRIATELY.

[Will_Restore]

Definitely one thing (storage configuration) I always use the GUI.  The only time I need to redo it is after hardware addition or swap.  That's like once a year?  Not worth the trouble to "automate" using command line, in my experience.

[raviteja_yedlap]

Hi,

Thanks Riaan Badenhorst and Will Restore for the help.

And another thing is that how many storage units can be created for tape drives,is there any limit and what is fargement size and should i give it manually or will it be enough to make it default.

Regards,

Raviteja

[RiaanBadenhorst]

Hi,

There is no limit (well I suppose there might be one but it probably huge) to the amount of storage units you can create. A storage unit is just used to address the tape drives. So your amount of storage units will depend on the amount of drives really, and if you're trying to logically segragate some drives and allocate them to certain jobs i.e. 10 drives available you'll make stu 1 with 4 and stu 2 with 6 so that jobs going to stu 1 can't take all 10 drives.....

See this note for fragment size https://www.veritas.com/support/en_US/article.TECH15692

[nbutech]

The more STU you will add the more overhead you will add on nbemm and nbrb.. so you may want to think what you want to achieve and have it configured accordingly

[raviteja_yedlap]

Thanks again Riaan Badenhorst and nbutech,

What is -cj option to add storage unit,will it be applicable for tape drives?

Regards,

Raviteja

[mph999]

-cj is max jobs - all th eoptions are explained in the command reference guide/ manpage.

Example of creating a robotic STU

bpstuadd -M nbmaster00 -label master_robot_0 -density hcart -cj 2 -nodevhost -rt tld -rn 0 -odo 0 -maxmpx 1 -mfs 100

[raviteja_yedlap]

Hi,

Thanks Martin.

Regards,

Raviteja