United States

Shopping













Norton
|
Small Business
|
Enterprise
|
Partners
|
Store
|
About Symantec


Overview
SoIutions






Products









Services





Training





Support




Security Response










Resources









ommunity







Store




Symantec.com > Business > Support > Search Results > KB Article













DOCUMENTATON: How to update NetBackup for a
replaced tape drive without deleting and re-adding the
drive
79.0:
TECH34296
,
70,90/:
2004-01-
11
,
&5/,90/:
2011-08-16
,
Article
URL http://www.symantec.com/docs/TECH34296
rticIe Type
Technical Solution


Product(s)
Show all


nvironment
Show all


Languages
Show all
ProbIem

DOCUMENTATON: How to update NetBackup for a replaced tape drive without deleting and re-adding the drive

SoIution

Manual: Veritas NetBackup (tmp) 6.0 Commands for UNX, Pages: 420-423
Modification Type: Supplement

Modification:
When a tape drive is replaced, the Veritas NetBackup (tmp) configuration will need to be updated to reflect the
changed drive.

Eight step procedure needs to be followed:

To swap a shared serialized drive or to update drive firmware on a shared drive
1 Down the drive. n the Device Monitor, select the drive to swap or update. From the Actions menu, select Down
Drive.

2 Replace the drive or physically update the firmware for the drive. f you replace the drive, specify the same SCS D
for the new drive as the old drive.

3 To produce a list of new and missing hardware, run tpautoconf -report_disc on one of the reconfigured servers. This
command scans for new hardware and produce a report that shows the new and the replaced hardware.

4 Ensure that all servers that share the new hardware are up and that all NetBackup services are active.

5 Run tpautoconf with the -replace_drive <drive name> -path <drive path> options or -replace_robot <robot number>
-path <robot path> options. The tpautoconf command reads the serial number from the new hardware device and
then updates the EMM database.

6 f the new device is an unserialized drive, run the device configuration wizard on all servers that share the drive. f
the new device is a robot, run the device configuration wizard on the server that is the robot control host.

7 Up the drive. n the Device Monitor, select the new drive. From the Actions menu, select Up Drive.

Here is an example but make sure the drive is "down" prior to running the tpautoconf -replace_drive. f it is not the
info could actually revert back to the old drive information:

Once the drive is replaced, run the following command to report the discrepancy:

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

This produces information similar to the following:

======================= New Device (Tape) ============
Inquiry = "QUANTUM DLT7000 245F"
Serial Number = PXA51S3232
Drive Path = /dev/rmt/21cbn
Found as TLD(0), Drive = 1
===================== Missing Device (Drive) =========
Drive Name = QUANTUMDLT70001
Drive Path = /dev/rmt/11cbn
Inquiry = "QUANTUM DLT7000 245F"
Serial Number = PXA51S3587
TLD(0) definition, Drive = 1
Hosts configured for this device:
Host = HJSTA
Host = HJSTB

This reports the discrepancy between the device database and the new device found. Take note of the new Drive
Path for the device as this will be needed for the tpautoconf command. To resolve this, run:

# cd /usr/openv/volmgr/bin
#./tpautoconf -replace_drive QUANTUMDLT70001 -path /dev/rmt/21cbn

Found a matching device in global DB, QUANTUMDLT70001 on host HJSTA
update of local DB on host HJSTA completed
globalDB update for host HJSTA completed

Found a matching device in global DB, QUANTUMDLT70001 on host HJSTB
update of local DB on host HJSTB completed
globalDB update for host HJSTB completed

This will update the global and local database to reflect the new device being replaced.

Up the drive at this point.


Below is an example for Windows:

...\Veritas\Volmgr\bin>tpautoconf -report_disc
======================= Missing Device (Drive) =======================
Drive Name = QUANTUM.SDLT320.000
Drive Path = {4,0,2,0}
nquiry = "QUANTUM SDLT320 5555"
Serial Number = RBF37Y6236
======================= New Device (Drive) =======================
nquiry = "QUANTUM SDLT320 5555"
Serial Number = RBF37Y6282
Drive Path = Tape0


The new device path syntax for Windows is not "Tape0" as suggested in the output above, but is actually the SCS
coordinates {port, bus, target, lun}, which can be acquired as per the following command:

...\Veritas\Volmgr\bintpautoconf -t
TPAC60 QUANTUM SDLT320 5555 RBF37Y6282 Tape0 - -



EXAMPLE using the needed device path syntax and observed success statement:

...\Veritas\Volmgr\bintpautoconf -replace_drive QUANTUM.SDLT320.000 -path
,4,0,5,0,
Found a matching device in global DB, QUANTUM.SDLT320.000 on host nbumedia

8 Restart media manager via command line for the tape drive(s).

UNX
/usr/openv/volmgr/bin/stoplid *** Stop media manager
/usr/openv/volmgr/bin/vmps *** Ensure ltid is stopped
/usr/openv/volmgr/bin/ltid *** Start media manager
/usr/openv/volmgr/bin/vmps *** Ensure ltid is started also with library drive should have tldd process running
as well

Windows
...\Veritas\Volmgr\bin>stopltid *** Stop media manager
...\Veritas\Volmgr\bin>ltid *** Start media manager sometimes may require to run "bpdown -v" and "bpup
-v"
...\Veritas\NetBackup\bin>bpps *** Ensure ltid is started also with library drive should have tldd process running
as well


Optionally could stop/start NetBackup on each of the SSO media servers that shares the tape drive or just the media
server that has the tape drive if not shared would also work.







ReIated rticIes

TECH43980 VERTAS NetBackup (tm) 6.0 Commands for UNX

Legacy ID

271366



Article URL http://www.symantec.com/docs/TECH34296


Terms of use for this information are found in Legal Notices
Email this article | PrintSubscribe via email
Login using SymAccount.
KnowIedge Base Search

My Support
reate a Support ase
Manage a Support ase
Manage Subscriptions
sk a Question on onnect(Symantec support Forums)
ontacting Support
maiI Support
ontact TechnicaI Support
FiIe a ase
Business riticaI Support Site
Support Forums
Rate this Article


Help us improve your support experience.



1995 - 2011 Symantec Corporation
About|
Site Map|
Legal|
Privacy|
Contact|
RSS

neL8ackup Medla Manager provldes lLs own drlver for communlcaLlng wlLh SCSlconLrolled roboLlc
perlpherals

1hls drlver ls called Lhe SCSA (Cenerlc SCSl passLhru drlver) also referred Lo as Lhe sg drlver

1o manage Lhe sg drlver

erform Lhe followlng sLeps as Lhe rooL user

1 ueLermlne lf an sg drlver ls loaded by uslng Lhe followlng command

/usr/sbln/modlnfo | grep sg

141 fc380000 2d8c 116 1 sg (SCSA Cenerlc 8evlslon 34d)

133 fc7fa000 1684 49 1 msgsys (SysLem v message faclllLy)

2 8emove Lhe exlsLlng drlver

/usr/sbln/rem_drv sg

/usr/bln/rm f /kernel/drv/sgconf

lnsLall SC urlver

1o lnsLall Lhe drlver run Lhe followlng command

/usr/openv/volmgr/bln/drlver/sglnsLall

Cnce Lhe drlver has been lnsLalled lL ls noL necessary Lo rebooL Lhe sysLem or run Lhe sglnsLall
command durlng or afLer each sysLem booL

Conflgurlng SC and S1 urlvers

1hls procedure conLalns lnsLrucLlons for conflgurlng Lhe sg drlver for SCSl LargeLs 0 Lhru 6 and 8 Lhru 13
for fasL or wlde adapLer cards

ln Lhls procedure you execuLe sgbulld Lo add Lhese LargeLs Lo Lhe sLconf sgconf and sgllnks flles
Ad[usL Lhe mL and ml parameLers Lo creaLe Lhe range of LargeLs and Luns requlred by your
conflguraLlon

1o conflgure drlvers

LxecuLe Lhe sgbulld scrlpL Lo add LargeL lus 06 813 and Luns 01 Lo Lhe followlng flles

/usr/openv/volmgr/bln/drlver/sLconf

/usr/openv/volmgr/bln/drlver/sgconf

/usr/openv/volmgr/bln/drlver/sgllnks

/usr/openv/volmgr/bln/sgbulld all mL 13 ml 1

1he mL 13 parameLer speclfles Lhemaxlmum LargeL lu LhaL ls ln use on any SCSl bus (or bound Lo a flbre
channel devlce)1he ml 1 parameLer speclfles Lhe maxlmum LargeL Lun LhaL ls ln use on any SCSl bus (or
by a flbre channel devlce)

1he flle /usr/openv/volmgr/bln/drlver/sLconf ls used Lo replace Lhe followlng seven enLrles ln Lhe
/kernel/drv/sLconf flle

name"sL" class"scsl" LargeL0 lun0

name"sL" class"scsl" LargeL1 lun0

name"sL" class"scsl" LargeL2 lun0

name"sL" class"scsl" LargeL3 lun0

name"sL" class"scsl" LargeL4 lun0

name"sL" class"scsl" LargeL3 lun0

name"sL" class"scsl" LargeL6 lun0

LdlL Lhe /kernel/drv/sLconf flle

lace a # ln column one of each llne of Lhe seven defaulL enLrles

1he Lemporary flle /sLconf conLalns Lhe enLrles LhaL you need Lo lnserL lnLo /kernel/drv/sLconf

8ebooL Lhe sysLem wlLh Lhe reconflgure opLlon (booL r or rebooL r)

verlfy LhaL Lhe sysLem creaLed devlce nodes for all Lhe Lape devlces uslng Lhe followlng command ls l
/dev/rmL/*cbn

lnsLall Lhe new sg drlver conflguraLlon

/usr/bln/rm f /kernel/drv/sgconf

/usr/openv/volmgr/bln/drlver/sglnsLall

when run sg lnsLall command sgconf wlll copy Lo /kernel/drv/sgconf

and sgllnks wlll copy Lo /eLc/devllnkLab

verlfy LhaL Lhe sg drlver found all Lhe roboLs Lape drlves

1he scrlpL /usr/openv/volmgr/bln/sgbulld adds Lhe proper enLrles Lo Lhe sgllnks and sgconf flles
8efore runnlng Lhe scrlpL make sure LhaL all devlces are powered on and connecLed Lo Lhe P8AAn
example of Lhe addlLlonal enLrles ln /usr/openv/volmgr/bln/drlver/sgconf

follows

name"sg" parenL"fp" LargeL0 lun0 fcporL wwn"22000090a30001c8rname"sg" parenL"fp"
LargeL0 lun1 fcporLwwn"22000090a30001c8r

An example of Lhe addlLlonal enLrles ln /usr/openv/volmgr/bln/drlver/sgllnks

follows

Lypeddl_pseudonamesgaddrw22000090a30001c80
sg/cn0LA1l0Lypeddl_pseudonamesgaddrw22000090a30001c81 sg/cn0LA1l1

revenLlng osslble SysLem roblems

vL8l1AS recommends addlng Lhe followlng forceload sLaLemenLs Lo Lhe /eLc/sysLem flle 1hese
sLaLemenLs prevenL Lhe sL and sg drlvers from belng unloaded from memory

forceload drv/sL

forceload drv/sg


CLher sLaLemenLs may be necessary for varlous flbre channel drlvers such as Lhe followlng example for
!nl drlvers 1hls sLaLemenL prevenLs Lhe named drlver from belng unloaded from memory

forceload drv/fcaw

SSC ConflguraLlons WlLh More 1han 16 1ape urlves

When Lhe number of Lape devlces LhaL are conflgured approaches 16 changes ln Lape devlce sLaLus may
noL be vlslble Lo all medla servers ln a Shared SLorage CpLlon (SSC) conflguraLlon 1hls ls because Lhe
defaulL maxlmum slze of lC message queues may noL be large enough

vL8l1AS recommends addlng Lhe followlng sLaLemenLs Lo Lhe /eLc/sysLem flle 1hese sLaLemenLs
lncrease Lhe maxlmum number of messages LhaL can be creaLed and Lhe number of byLes per queue A
rebooL ls necessary for Lhe changes Lo Lake effecL

seL msgsysmsglnfo_msgLql312

seL msgsysmsglnfo_msgmnb63336

hLLp//wwwmassdk/fllesecLlon/caL_vlew/39neLbackupscrlpLshLml for scrlpLlng samples neLbackup