Veritas Netbackup Command Line Guide

This is just my own notes on Veritas Netbackup Command Line Guide, feel free to copy-paste;-):
————————————————————————————-
/usr/openv/netbackup/bin/jnbSA >>run NBU GUI
/usr/openv/netbackup/bin/bpadm >>NBU Menu Interface
/usr/openv/volmgr/bin/vmquery -deassignbyid QOSFEB 1 0 >>deassign media
/usr/openv/netbackup/bin/admincmd/bpexpdate -m QOSFEB -d 0 -force >>Expired
/usr/openv/netbackup/bin/admincmd/bpclient -client aziz -L >
/usr/openv/netbackup/bin/admincmd/bpclient -client aziz -add -max_jobs 99 >>set max jobs to 99
/usr/openv/netbackup/bin/bplist -C aziz -t 4 -R / >>chek list file that backed up already
/usr/openv/netbackup/bin/bpbackup -i -p test -s full -S sunserver1 >>Run jobs
/usr/openv/volmgr/bin/ltid -nsu >>robot will’t unload tape
/usr/openv/volmgr/bin/stopltid >>stop ltid
/usr/openv/netbackup/bin/admincmd/bperror -statuscode 96 >>explanation error
/usr/openv/netbackup/bin/admincmd/bpbackupdb >>backup catalog
/usr/openv/netbackup/bin/bpclntcmd -pn >>query master server communication
/usr/openv/netbackup/bin/bpclntcmd -sv >>query master server version
/usr/openv/netbackup/bin/admincmd/get_license_key >>add/remove license key

#/usr/openv/netbackup/bin/admincmd/:
bpmedia -movedb -ev -oldserver -newserver
bpmedia -movedb -ev PR0161 -oldserver drsskdb1 -newserver masterbackup >>move database to newserver

bpimage -newserver masterbackup -oldserver drsskdb1 -id BI0336 >>

/usr/openv/volmgr/bin/vmoprcmd -crawlreleasebyname

/usr/openv/netbackup/bin/bpdbm -consistency >>Catalog Backup Integrity check

Restore Catalog:
—————–
/usr/openv/netbackup/bin/admincmd/bprecover –help
/usr/openv/netbackup/bin/admincmd/bprecover -r all -dpath f: >>restore dari catalog di disk
/usr/openv/netbackup/bin/admincmd/bprecover -l -m L1001 -d dlt >>tape model dlt
/usr/openv/netbackup/bin/admincmd/bprecover -l -m L1001 -d 8mm >>tape model 8mm
/usr/openv/netbackup/bin/admincmd/bprecover -r all -tpath /dev/rmt/0cbn >>
bprecover -l -tpath /dev/rmt/hc2d4
————

{Verify the Netbackup communication daemons are listening for request:
netstat -a |grep bpcd
netstat -a |grep vnetd

{UNFREEZE TAPE MEDIA MARKED AS FROOZEN:
/usr/openv/netbackup/bin/admincmd/bpmedia -unfreeze -m JKT738L4
/usr/openv/netbackup/bin/admincmd/bpmedia -unfreeze -m JKT626L4

c:\Program Files\Veritas\Netbackup\bin> bpmedia -unfreeze -m -h
c:\Program Files\Veritas\Netbackup\bin\admincmd\bppllist -U -allpolicies
c:\Program Files\Veritas\Netbackup\bin\admincmd\bppllist -L -allpolicies
c:\Program Files\Veritas\Netbackup\bin\admincmd\bpmedialist -summary
c:\Program Files\Veritas\Netbackup\bin\goodies\available_media

{Remove information about existing media ID from NBU Catalog then delete the existing media ID:
/usr/openv/netbackup/bin/admincmd/bpexpdate -d 0 -m

{initiate import media ID JKT152:
./bpimport -create_db_info -id JKT152

——————————————————————————————–
TUNING AND TWEAKING:

/usr/openv/netbackup
cat /usr/openv/netbackup/NET_BUFFER_SZ
65536

For example, a Network Buffer Size of 64KB could be configured and checked like this:
# echo “65536” > /usr/openv/netbackup/NET_BUFFER_SZ
# cat /usr/openv/netbackup/NET_BUFFER_SZ
65536

/usr/openv/netbackup/db/config:
NUMBER_DATA_BUFFERS
SIZE_DATA_BUFFERS
NUMBER_DATA_BUFFERS_RESTORE

NUMBER_DATA_BUFFERS:
8 for non-multiplexed backups
4 for multiplexed backups
8 for non-multiplexed restore, verify, import and duplicate

SIZE_DATA_BUFFERS:
32768 for non-multiplexed backups
65536 (64512 on Solaris) for multiplexed backups

NUMBER_DATA_BUFFERS_RESTORE:
12 (only effects restores of multiplexed backups)

—-
tpautoconf -report_disc , this command will list what device that had been missing or found.
tpautoconf -replace_drive drive_name –path drive_path, this command will update the existing device

{STOP NEXT SHCEDULE BACKUP REQUEST:
bprdreg -terminate >>WILL STOP BPRD services

{SHARED SYMANTEC PROCESS:
check with bpps -x command:

/opt/VRTSpbx/bin/vxpbx_exchange start
/opt/VRTSpbx/bin/vxpbx_exchange stop

Veritas NetBackup 6.5 and 6.5.x Manuals and links

6.5.x Release Updates
The 6.5.x Release Updates provide documentation updates for the additional features provided in each release. The links to the documentation updates for each version is as follows:
-6.5.4 Release Update:
-6.5.3 Release Update:

Step Upgrading to Veritas Netbackup 6

Step by Rakesh Khandelwal:

First check release notes to make sure H/W and O/S you are about to use is supported or not. Release Notes for UNIX and Windows (http://support.veritas.com/docs/279259 )
Symantec’s Upgrade Guide, Version “B” ( http://support.veritas.com/docs/285590 )

Assuming you have already checked databse consistency and resolved any known or preexisting consistency issues or catalog inconsistencies

Step 1 : Prepare, Upgrade and Patcvh the Master Server

  1. Backup the catalogs
  2. In a c clustered environment, take NetBackup offline.
  3. Deactivate all policies.
  4. On Solaris Only, uninstall the old version of NetBackup.
  5. Upgrade the software:
  6. Stop all services.
  7. run the installation.
  8. Apply the latest maintenance packs.
    NOTE : For Windows clustered environments, perform NetBackup upgrade installations from the system console, not from a Remote Terminal Services sessions.

Step 2: Populate the EMM database

  1. Ensure that the daemons or services and processes are running.
  2. Run nbpushdata -add on the ipgraded systems in the following order:
    a) The host that was the 5.x Global Device Database host
    b) All upgraded master servers
    c) All upgraded 5.x Volume Database hosts
  3. Restart the services/daemons.
  4. Run nbpushdata -modify_5x_hosts on all 6.0 master servers.


Step 3: Upgrade the NetBackup Remote Administration Console System and any addition components

1.Stop all services/daemons

2.Run the installation.

3.Apply the latest maintenace packs.

4.Restart the services/daemons.

5.Upgrade and add-on components.

6.Install the latest maintenance packs for the add-on components.


Step 4: Prepare, upgrade and Patch the Media servers

  1. On Solaris only, uinstall the old version of NetBackup.
  2. Upgrade the software:
    a) Stop all services/daemons.
    b) Run the instalation.
  3. Apply the latest maintenance packs.
  4. Restart the services/daemons.
  5. Populate the EMM database:
    nbpushdata -add

Step 5: Upgrade the clients

  1. Perform local or remote client upgrades.
  2. Install the latest maintenance packs.

Step 6: Complete and Test the upgrade

  1. Activate the policies
  2. Run test backup jobs.
  3. Backup the catalogs.

Additional Information from Dennis Strom:

here all the info I have on upgrading. I even included a link to this post since I really liked Rakesh’s post.

Other link:

Upgrading to Veritas NetBackup 6.0 on Supported Windows Platforms

VERITAS NetBackup 6.0 Release Notes, for UNIX, Windows, and Linux

Upgrading to Veritas NetBackup 6.0

VERITAS NetBackup 6.0

How to restore LTO1 or 2 on LTO 3 Drive

For many reason, I re-post again about this issue; How to restore LTO1 or 2 on LTO 3 Drive…

The procedure is as follows:

  1. Inject the tape into the ACS library, then perform a robot inventory of the ACS library.

  2. After the volume database is updated, the RobotType of the media will change to “ACS” and the tapes should be recognized as “hcart”.

  3. Run “vmchange -new_mt <new density> -m <media ID>” to change the density. <new density> should be “hcart3” for the LTO Gen-3 drive and <media ID> refers to the media barcode. An eg would be “vmchange -new_mt hcart3 -m dx0333”

  4. Run “vmquery -m <mediaID>” to check that the density have been updated to “hcart3” from “hcart”.

  5. Run “bpmedia -changeden -new <density> -ev <mediaID>”

  6. eg “bpmedia -changeden -new hcart3 -ev dx0333” Note: This command will take some time to complete. Please be patient and let it complete on it’s own. If terminated halfway, strange things may occur later.

  7. Run “bpmedialist -m <mediaID>” to check that the density have been updated.

  8. Run the normal restoration procedure to restore the data from the LTO Gen1 tapes using the ACS library.

  9. Once, we have completed the restoration, the tape should be ejected from the ACS library to prevent it from being used for future backups. If necessary, will need to execute the commands in Step 3 and 5 to change the density back to “hcart”.

“Cannot find VRTSperl to execute”

I got this error while installing Netbackup 6 on Solaris 10 Sparc:

“the following package(s) are mising and must be installed before Netbackup can be installed:”
VRTSpbx

——-

It means that VRTSpbx must be installed before continue to install Netbackup 6.

Eject Netbackup CD, and mount ICS CD (Infrastructure Core Services v.1.2.3.45) then run installics script,

it give me another error:

“cannot find VRTSperl to execute”

Ok, this another dependencies, I need to install VRTSperl before install VRTSpbx. But it quite strange because I can’t find VRTSperl package on ICS or Netbackup CD.

So if u have same problem, you need to install VRTSperl package. can be found on Veritas Storage Foundation v.4.1 CD.

Install this package :

#gunzip VRTSperl.tar.gz

#tar -xvf VRTSperl.tar

#pkgadd -d .

The following packages are available:
1  VRTSperl     Perl 5.8.0 for VERITAS
(sparc) 4.0.2

Select package(s) you wish to process (or ‘all’ to process
all packages). (default: all) [?,??,q]: all

——

Then continue with the ICS installation:

#./installics

Note: Please avoid to run script like this:

“/cdrom/nb_60_ics_1.2.3.45_solaris/./installics”

you will get error like this:

Can’t locate VxIF/TrainInstaller.pm in @INC (@INC contains: /opt/ VRTSperl/lib/5.8.0/sun4-solaris-thread-multi /opt/VRTSperl/lib/5. 8.0 /opt/VRTSperl/lib/site_perl/5.8.0/sun4-solaris-thread-multi / opt/VRTSperl/lib/site_perl/5.8.0 /opt/VRTSperl/lib/site_perl .) a t /cdrom/nb_60_ics_1.2.3.45_solaris/./installics line 3.

So, U have to change directory to “/cdrom/nb_60_ics_1.2.3.45_solaris/” then run the script “./installics” from there.

After install and configure ICS, move on with the Netbackup 6 Installation..

Update:

download VRTSperl package here:

http://www.ziddu.com/download/5664289/VRTSperl.tar.gz.html

Decommision Media Server

When a media server is decommisioned b4 removing from Netbackup , plz follow the below steps to make the setup stable once again.

Step 1 : go to server host properties & delete the media server name in the “Media server” List & also in the “server” list.

Step 2. Remove the storage unit which belongs to the particular decomissioned media

Step 3 : stop all the services then, Go to \install path\volmgr\database.

Rename the below files. globdb, robtic_def & ltdevis to .old
go to misc folder & delete all the files except the robotic_def directory.
get inside to this robotic_def dir & delete the files.

Step 4. start all the netbackup services

Open cmd promt & go to volmgr\bin dir
type

vmglob -set_gdbhost

Step 5. go to configure storage devices wizard. you can still see the decommisioned media server entry checkbox.

Delete the decomissioned media server entry alone & discover the conf storage device for the remaining servers

Now u will be able to run bpmedialist without any issues. Some of the tapes will show DBBackup status. You can bring them to scratch or secure the data. (solution given in previously for other person). run thru the forum for this.

This is the solution for ur query & nothing more u need.

Thank’s to Ranjith Kumar. J for the article..

Replace drive in SSO environment

In case one of our customer had drive replacement it’s mean that serial number also change. So in order to update the serial number in SSO environment. Here’s the steps.

1. tpautoconf -report_disc , this command will list what device that had been missing or found.
2. tpautoconf -replace_drive drive_name –path drive_path, this command will update the existing device configuration with the new one.

———
#cd /usr/openv/volmgr/bin
#tpautoconf -report_disc
===== Missing Device (Drive) =====
Drive Name = IBMULTRIUM3-TD03
Drive Path = /dev/rmt/c36t6d0BESTnb
Inquiry = “IBM ULTRIUM-TD3 64D0”
Serial Number = xxxxxxxxxxxx
ACS(4) definition ACS = 0 LSM = 0 PANEL = 1 DRIVE = 4
Hosts configured for this device:
Host = xxxxxxxxxxxx
Host = xxxxxxxxxxxx

=====Missing Device (Drive) =====
Drive Name = IBMULTRIUM3-TD02
Drive Path = /dev/rmt/c35t6d0BESTnb
Inquiry = “IBM ULTRIUM-TD3 64D0”
Serial Number = xxxxxxxxxxxx
ACS(4) definition ACS = 0 LSM = 0 PANEL = 1 DRIVE = 8
Hosts configured for this device:
Host = xxxxxxxxxxxx
Host = xxxxxxxxxxxx

===== Missing Device or no local control path (Robot) =====
Defined as robotic ACS(4)
Inquiry = “-”
Serial Number =
Robot Control Host = xxxxxxxxxxxx
Hosts configured for this device:
Host = xxxxxxxxxxxx
Host = xxxxxxxxxxxx

===== New Device (Tape) =====
Inquiry = “HP C5683A C305”
Serial Number = xxxxxxxxxxxx
Drive Path = /dev/rmt/c4t0d0BESTnb
===== New Device (Tape) =====
Inquiry = “IBM ULTRIUM-TD3 64D0”
Serial Number = xxxxxxxxxxxx
Drive Path = /dev/rmt/c35t6d0BESTnb
===== New Device (Tape) =====
Inquiry = “IBM ULTRIUM-TD3 5BG2”
Serial Number = xxxxxxxxxxxx
Drive Path = /dev/rmt/c36t6d0BESTnb
# tpautoconf -replace_drive IBMULTRIUM3-TD02 -path /dev/rmt/c35t6d0BESTnb
Found a matching device in global DB, IBMULTRIUM3-TD02 on host xxxxxxxxxxxx
update of local DB on host xxxxxxxxxxxx completed
globalDB update for host xxxxxxxxxxxx completed
Found a matching device in global DB, IBMULTRIUM3-TD02 on host xxxxxxxxxxxx
etc…

etc…

————–

Device Configuration must be run on all servers to complete drive replacement

Configure Netbackup Device (Robot & drive) on AIX

Hardware :
Sun Storagetek L40 with SCSI LVD/SE.
2 drive : Seagate LT01 and SDLT 320
SCSI ID : Robotic = 6
Drive 0 = 0
Drive 1 = 1
———

1. run command : lsdev –C –c adapter (to determine the logical indetifier for the SCSI controler)
# lsdev -C -c adapter
ent0 Available 10-80 IBM 10/100 Mbps Ethernet PCI Adapter (23100020)
fda0 Available 01-D1 Standard I/O Diskette Adapter
mg20 Available 10-70 GXT130P Graphics Adapter
paud0 Available 01-Q2 Ultimedia Integrated Audio
ppa0 Available 01-R1 CHRP IEEE1284 (ECP) Parallel Port Adapter
sa0 Available 01-S1 Standard I/O Serial Port
sa1 Available 01-S2 Standard I/O Serial Port
scsi0 Available 10-60 Wide/Fast-20 SCSI I/O Controller (used for CDROM & SCSI Hardisk)
scsi1 Available 10-88 Wide/Ultra-2 SCSI I/O Controller (Tape & robotic)

sioka0 Available 01-K1-00 Keyboard Adapter
siokma0 Available 01-K1 Keyboard/Mouse Adapter
sioma0 Available 01-K1-01 Mouse Adapter
siota0 Available 01-Q1 Tablet Adapter

2. run command : lsdev –C –s scsi (to display the SCSI device files)
# lsdev -C -s scsi
cd0 Available 10-60-00-1,0 16 Bit SCSI Multimedia CD-ROM Drive
hdisk0 Available 10-60-00-9,0 16 Bit LVD SCSI Disk Drive
rmt0 Available 10-88-00-0,0 Other SCSI Tape Drive
rmt1 Available 10-88-00-1,0 Other SCSI Tape Drive

Note:
Detected two drives, but robotic didn’t detected.

3. to detect robot, run this command :
#cd /usr/openv/volmgr/bin/driver
#./install_ovpass {to install the SCSI passthru driver}

Then run:
#mkdev -c media_changer -s scsi -t ovpass -p controller -w id,lun

Where:
◆ controller is the logical identifier of the drive’s SCSI adaptor, such as scsi0, scsi1 or vscsi1.
◆ id is the SCSI ID of the robotic connection.
◆ scsi_id is the fibre channel identifier for the N_Port address (D_ID) of the robotic connection.
◆ lun is the logical unit number of the robotic connection.

Example:
# mkdev -c media_changer -s scsi -t ovpass -p scsi1 -w 6,0

4. run command : lsdev –C –s scsi (to display the SCSI device files)
# lsdev -C -s scsi
cd0 Available 10-60-00-1,0 16 Bit SCSI Multimedia CD-ROM Drive
hdisk0 Available 10-60-00-9,0 16 Bit LVD SCSI Disk Drive
ovpass0 Available 10-88-6,0 VERITAS Media Changer {SCSI device driver for robotic}
rmt0 Available 10-88-00-0,0 Other SCSI Tape Drive {SCSI device driver for drive0)
rmt1 Available 10-88-00-1,0 Other SCSI Tape Drive {SCSI device driver for drive1)

5. make sure with the performing command: ./scan from /usr/openv/volmgr/bin/
#cd /usr/openv/volmgr/bin
# ./scan
************************************************************
*********************** SDT_TAPE ************************
*********************** SDT_CHANGER ************************
*********************** SDT_OPTICAL ************************
************************************************************
————————————————————
Device Name : “/dev/rmt0.1”
Passthru Name: “/dev/rmt0.1”
Volume Header: “”
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry : “SEAGATE ULTRIUM06242-XXX1619”
Vendor ID : “SEAGATE ”
Product ID : “ULTRIUM06242-XXX”
Product Rev: “1619”
Serial Number: “xxx”
WWN : “SEAGATE ULTRIUM06242-XXX ”
WWN Id Type : 1
Device Identifier: “SEAGATE ULTRIUM06242-XXX”
Device Type : SDT_TAPE
NetBackup Drive Type: 3
Removable : Yes
Device Supports: SCSI-3
Flags : 0x4
Reason: 0x0
————————————————————
Device Name : “/dev/rmt1.1”
Passthru Name: “/dev/rmt1.1”
Volume Header: “”
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry : “QUANTUM SDLT320 5E5E”
Vendor ID : “QUANTUM ”
Product ID : “SDLT320 ”
Product Rev: “5E5E”
Serial Number: “xxx”
WWN : “QUANTUM SDLT320 xxx”
WWN Id Type : 1
Device Identifier: “QUANTUM SDLT320 xxx ”
Device Type : SDT_TAPE
NetBackup Drive Type: 11
Removable : Yes
Device Supports: SCSI-2
Flags : 0x4
Reason: 0x0
————————————————————
Device Name : “/dev/ovpass0”
Passthru Name: “/dev/ovpass0”
Volume Header: “”
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry : “STK L40 xxx”
Vendor ID : “STK ”
Product ID : “L40 ”
Product Rev: “0215”
Serial Number: “LLC0220xxx”
WWN : “”
WWN Id Type : 0
Device Identifier: “”
Device Type : SDT_CHANGER
NetBackup Robot Type: 8
Removable : Yes
Device Supports: SCSI-3
Number of Drives : 0
Number of Slots : 0
Number of Media Access Ports: 0
Flags : 0x0
Reason: 0x0
# lsdev -C -s scsi
cd0 Available 10-60-00-1,0 16 Bit SCSI Multimedia CD-ROM Drive
hdisk0 Available 10-60-00-9,0 16 Bit LVD SCSI Disk Drive
ovpass0 Available 10-88-6,0 VERITAS Media Changer
rmt0 Available 10-88-00-0,0 Other SCSI Tape Drive
rmt1 Available 10-88-00-1,0 Other SCSI Tape Drive
# lsdev -C -c adapter
ent0 Available 10-80 IBM 10/100 Mbps Ethernet PCI Adapter (23100020)
fda0 Available 01-D1 Standard I/O Diskette Adapter
mg20 Available 10-70 GXT130P Graphics Adapter
paud0 Available 01-Q2 Ultimedia Integrated Audio
ppa0 Available 01-R1 CHRP IEEE1284 (ECP) Parallel Port Adapter
sa0 Available 01-S1 Standard I/O Serial Port
sa1 Available 01-S2 Standard I/O Serial Port
scsi0 Available 10-60 Wide/Fast-20 SCSI I/O Controller
scsi1 Available 10-88 Wide/Ultra-2 SCSI I/O Controller
sioka0 Available 01-K1-00 Keyboard Adapter
siokma0 Available 01-K1 Keyboard/Mouse Adapter
sioma0 Available 01-K1-01 Mouse Adapter
siota0 Available 01-Q1 Tablet Adapter
#

6. ALL DETECTED NOW!!
To ensure the driver device files are accessible after each system boot, the following command should be placed in the systemstartup script:
/usr/openv/volmgr/bin/driver/mkdev_ovpass

7. If u get an error, maybe there caused by the SCSI connection.
to remove the SCSI passthru driver, run : ./remove_ovpass from /usr/openv/volmgr/bin/driver

Netbackup – How do I expire, delete tapes from the database?

First you need to make sure that there are no valid images on the tape that you want.
NetBackup\bin\admincmd\bpimmedia -mediaid -L

If there are no images that you need, expire the tape:
NetBackup\bin\admincmd\bpexpdate -m -d 0 -host -force
This expires the images in the media database which resides specifically on the media server.

Verify that the images have been expired by re-running:
NetBackup\bin\admincmd\bpimmedia -mediaid -L

Now make sure that the tape is deleted from the volume manager on the master server. This step is automatically run by Veritas twice a day, and if you have used bpexpdate the tape will be removed but you can force it to take effect immediately:
volmgr\bin\vmquery -m
This gets some information on the tape such as its assigned date, pool number and status. If the status is anything other that 0x0, that issue needs to be resolved first – The most likely issue is a Frozen tape – IT must be unfrozen before you deassign it.

To unfreeze a tape:
NetBackup\bin\admincmd\bpmedia -unfreeze -m -h
If the tape was suspended you can replace -unfreeze with -unsuspend

If you are unsure which media server the tape belongs to:
NetBackup\bin\admincmd\bpimmedia -L -mediaid

This step will deassign and remove the volume images.
Volmgr\bin\vmquery -deassignbyid

Finally delete the tape:
volmgr/bin/vmdelete -m

Thats all!!

How to Configure Tape Drive on Solaris for Veritas Netbackup

Understanding the SCSI Passthru Drivers

NetBackup Media Manager provides its own driver for communicating with SCSI-controlled robotic peripherals.

This driver is called the SCSA (Generic SCSI passthru driver), also referred to as the sg driver.

To manage the sg driver

Perform the following steps as the root user.

1. Determine if an sg driver is loaded by using the following command:

/usr/sbin/modinfo | grep sg

141 fc580000 2d8c 116 1 sg (SCSA Generic Revision: 3.4d)

153 fc7fa000 1684 49 1 msgsys (System V message facility)

2. Remove the existing driver:

/usr/sbin/rem_drv sg

/usr/bin/rm -f /kernel/drv/sg.conf

Install SG Driver

To install the driver run the following command:

/usr/openv/volmgr/bin/driver/sg.install

Once the driver has been installed, it is not necessary to reboot the system or run the sg.install command during or after each system boot.

Configuring SG and ST Drivers

This procedure contains instructions for configuring the sg driver for SCSI targets 0 thru 6 and 8 thru 15 for fast or wide adapter cards.

In this procedure, you execute sg.build to add these targets to the st.conf, sg.conf and sg.links files. Adjust the -mt and -ml parameters to create the range of targets and LUNs required by your configuration.

To configure drivers

Execute the sg.build script to add target IDs 0-6, 8-15, and LUNs 0-1 to the following files:

/usr/openv/volmgr/bin/driver/st.conf

/usr/openv/volmgr/bin/driver/sg.conf

/usr/openv/volmgr/bin/driver/sg.links

/usr/openv/volmgr/bin/sg.build all -mt 15 -ml 1

The -mt 15 parameter specifies themaximum target ID that is in use on any SCSI bus (or bound to a fibre channel device).The -ml 1 parameter specifies the maximum target LUN that is in use on any SCSI bus (or by a fibre channel device).

The file /usr/openv/volmgr/bin/driver/st.conf is used to replace the following seven entries in the /kernel/drv/st.conf file:

name=”st” class=”scsi” target=0 lun=0;

name=”st” class=”scsi” target=1 lun=0;

name=”st” class=”scsi” target=2 lun=0;

name=”st” class=”scsi” target=3 lun=0;

name=”st” class=”scsi” target=4 lun=0;

name=”st” class=”scsi” target=5 lun=0;

name=”st” class=”scsi” target=6 lun=0;

Edit the /kernel/drv/st.conf file.

Place a # in column one of each line of the seven default entries.

The temporary file ./st.conf contains the entries that you need to insert into /kernel/drv/st.conf.

Reboot the system with the reconfigure option (boot -r or reboot — -r).

Verify that the system created device nodes for all the tape devices using the following command: ls -l /dev/rmt/*cbn

Install the new sg driver configuration.

/usr/bin/rm -f /kernel/drv/sg.conf

/usr/openv/volmgr/bin/driver/sg.install

when run sg install command sg.conf will copy to /kernel/drv/sg.conf

and sg.links will copy to /etc/devlink.tab

Verify that the sg driver found all the robots, tape drives,

The script /usr/openv/volmgr/bin/sg.build adds the proper entries to the sg.links and sg.conf files. Before running the script, make sure that all devices are powered on and connected to the HBA.An example of the additional entries in /usr/openv/volmgr/bin/driver/sg.conf

follows:

name=”sg” parent=”fp” target=0 lun=0 fc-port- wwn=”22000090a50001c8″;name=”sg” parent=”fp” target=0 lun=1 fc-port-wwn=”22000090a50001c8″;

An example of the additional entries in /usr/openv/volmgr/bin/driver/sg.links

follows:

type=ddi_pseudo;name=sg;addr=w22000090a50001c8,0; sg/c\N0t\A1l0type=ddi_pseudo;name=sg;addr=w22000090a50001c8,1; sg/c\N0t\A1l1

Preventing Possible System Problems

VERITAS recommends adding the following forceload statements to the /etc/system file. These statements prevent the st and sg drivers from being unloaded from memory

forceload: drv/st

forceload: drv/sg

 

Other statements may be necessary for various fibre channel drivers, such as the following example for JNI drivers. This statement prevents the named driver from being unloaded from memory.

forceload: drv/fcaw

SSO Configurations With More Than 16 Tape Drives

When the number of tape devices that are configured approaches 16, changes in tape device status may not be visible to all media servers in a Shared Storage Option (SSO) configuration. This is because the default maximum size of IPC message queues may not be large enough.

VERITAS recommends adding the following statements to the /etc/system file. These statements increase the maximum number of messages that can be created, and the number of bytes per queue. A reboot is necessary for the changes to take effect.

set msgsys:msginfo_msgtql=512

set msgsys:msginfo_msgmnb=65536