DOCUMENTATION: How to update NetBackup for a replaced tape drive without deletin g and re-adding the driveArticle: TECH34296

Created: 2004-01-11 Update d: 2010-01-29 Article URL http://www.symantec.com/docs/TECH34296 Article Type Technical Solution Product(s) Show all CLOSE X NetBackup Enterprise Server7.06.5, 6.05.1, 5.0

Environment Show all CLOSE X Solaris8.0 Windows Server 2003Standard Server SP2 (x64), Standard Server SP2

Languages Show all CLOSE X English Problem DOCUMENTATION: How to update NetBackup for a replaced tape drive without deletin g and re-adding the drive Solution Manual: Veritas NetBackup (tmp) 6.0 Commands for UNIX, Pages: 420-423 Modification Type: Supplement Modification: When a tape drive is replaced, the Veritas NetBackup (tmp) configuration will ne ed to be updated to reflect the changed drive. Eight step procedure is needs to be followed: To swap a shared serialized drive or to update drive firmware on a shared drive 1 Down the drive. In the Device Monitor, select the drive to swap or update. Fro m the Actions menu, select Down Drive. 2 Replace the drive or physically update the firmware for the drive. If you repl ace the drive, specify the same SCSI ID 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 produc e 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 NetBac kup 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 com mand reads the serial number from the new hardware device and then updates the E MM database. 6 If the new device is an unserialized drive, run the device configuration wizar d on all servers that share the drive. If the new device is a robot, run the dev ice configuration wizard on the server that is the robot control host. 7 Up the drive. In the Device Monitor, select the new drive. From the Actions me nu, select Up Drive. Here is an example but make sure the drive is "down" prior to running the tpauto conf -replace_drive. If 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 = HOSTA Host = HOSTB This reports the discrepancy between the device database and the new device foun d. 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 HOSTA update of local DB on host HOSTA completed globalDB update for host HOSTA completed Found a matching device in global DB, QUANTUMDLT70001 on host HOSTB update of local DB on host HOSTB completed globalDB update for host HOSTB completed This will update the global and local database to reflect the new device being r eplaced.

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} Inquiry = "QUANTUM SDLT320 5555" Serial Number = RBF37Y6236 ======================= New Device (Drive) ======================= Inquiry = "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 SCSI coordinates {port, bus, target, lun}, which can be acquired as per the following command: ...\Veritas\Volmgr\bin>tpautoconf -t TPAC60 QUANTUM SDLT320 5555 RBF37Y6282 4 0 5 0 Tape0 - -

EXAMPLE using the needed device path syntax and observed success statement: ...\Veritas\Volmgr\bin>tpautoconf -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). UNIX /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 lib rary 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 librar y drive should have tldd process running as well Optionally could stop/start NetBackup on each of the SSO media servers that shar es the tape drive or just the media server that has the tape drive if not shared would also work.