Replace tape library

[IT_guys]

Hi 

I use the NetBackup Server, Unix, Enterprise Server, v6.0 , plan to replace the new tape library with the model C4 Sun Storage.  

May I know the step to NBU configuration before replace the new tape and new devices? 

I find the step on the NBU configuration when replace the new tape drive.  Is it the same procedure for Tape library.  Please kindly to advice. Many thanks

1- check the drive and make sure no media stuck in the drive
if there is
then eject the Media and move the media to a tape slot
then run inventory robot .. use NetBackup Admin Console GUI
Media and Device Management --> Devices --> Robots --> Actions --> inventory Robot
select the option "update Volume configuration" --> Start

2- delete the drive .. using NetBackup Admin Console GUI

3- Restart NetBackup
- make sure no backup, duplication or restore jobs currently running

- stop NetBackup
# /usr/openv/netbackup/bin/bp.kill_all

- verify all daemons are terminated
# /usr/openv/netbackup/bin/bpps -a

- start NetBackup
# /usr/openv/netbackup/bin/goodies/netbackup start

- verify all daemons are running
# /usr/openv/netbackup/bin/bpps -a

4- make note of the new drive Serial number
After replacing the Tape Drive

- verify the Operating System can discover All 4 x Tape Drives
# /usr/openv/volmgr/bin/sgscan conf -v

- verify NetBackup can discover the drives
# /usr/openv/volmgr/bin/tpautoconf -t

# /usr/openv/volmgr/bin/scan -tape

Notice : verify the New Drive Serial number is discovered ...

5- To configure the drive
Use the GUI Device Configuration Wizard --> Media and Device Management --> Configure Storage Unit --> device Configuration Wizard --> run the Auto-discovery

6- the Wizard might restart NBU (device daemons) again
if not then restart ltid again
# /usr/openv/volmgr/bin/stopltid
# /usr/openv/volmgr/bin/ltid -v

7- finally verify the new drive is configured
use either NetBackup Admin Console GUI
or run the Following command
# /usr/openv/volmgr/bin/tpconfig -d

[Marianne]

NetBackup 6.0?

Oh dear!! That was the worst ever version of NBU and ran out of support MANY years ago.

If your company perceives backup important enough to purchase a new library, they really need to ensure that the backup server and software is also latest and greatest.

Rant over...

I have posted steps to replace a tape library over here:

https://vox.veritas.com/t5/NetBackup/Changing-tape-library/td-p/347963

[IT_guys]

Hi ,

I am very sorry to miss your email for the steps , I use another method to do so.

As the company not to invest any money to do the upgrade, so it still use the old version on solaris 9 platform. 

 I down the drive and remove all the STU, TLD and Drive on the console. then run the below steps.

1. Rmove all STU, TLD and Drive and stop the netbackup 

Add the new library and run the netbackup 

2. Sgscan conf -v 

3. tpconfig -l to show library has two drives.

4. scan -all to scan all devices 

#Step 4, I can see the Tape library and drives.

5, Add the device configuration on Admin Console. 

#The robot orginal to use TLD(0) , after replace the robot, it add the TLD 6, and two tape drives. 

6. I use robot test, it shows mode_sense failed 

7. I try to run the policy to use the tape backup , but the detail message show 

A pending request has been generated for this resouce request

Operator action may be required. Pending Action: No Action 

Media ID : CP0063, Barcode :CP0063L3, Density : hcart 3 Accessmode : Write 

I check the active monitor to show icon is waiting , it seems to be not work after replacement.  

Can you please advice what is the problem and how to fix it ?

[Will_Restore]

Solaris 9?  Oh my! 

At any rate. see this ancient thread about mode sense fail:

https://vox.veritas.com/t5/NetBackup/robtest-commands-mode-sense-failing/m-p/151962#M18568

[Marianne]

There is no point in carrying on after this:

I use robot test, it shows mode_sense failed 

You seem to be missing some steps here:

Add the new library and run the netbackup

Did you shutdown the server to physically remove the library and attach the new one?

Did you check that new devices are visible and accessible at OS level before doing anything in NetBackup?

Please show us output of 'scan', 'sgscan' and 'tpconfig -l'.

Or else review my steps and start over... 
Forget about NBU until OS commands (such as cfgadm) sees the devices.
Solaris normally needs the sg driver to be rebuilt before commands such as sgscan and scan will report devices correctly.

Only re-config devices when scan and sgscan reports devices correctly and you are sure that old devices have been deleted properly from NBU followed by a restart.

[IT_guys]

Did you shutdown the server to physically remove the library and attach the new one?

As the enviornment not allow to add new library to another host, i just only connect to one server, then run the command to do. 

Before remove the tape library, I down the drive only, and stop netbackup.

After add the library, i use devfsadm -C and sgscan conf -v then start the netbacup, and use device wizard to add new library. In the first time to do, I am not delete the device and Tape library.  

After it is not good, I try to remove the all device on the admin console and run the scan and tpconfig -l , then restart the netbackup and add device on the console. 

Did you check that new devices are visible and accessible at OS level before doing anything in NetBackup? 

Yes I run the sgscan conf -v and scan -a to see the OS and NBU able to see the Device. 

[Marianne]

It seems you clearly do not need my advice.

Good luck.

[IT_guys]

Hi 

I follow your previous step to fix the problem.

1. Remove the Drive, STU and Robot.

2. Remove content in /dev/rmt/

3 Stop the netbackup 

4. Reboot -- -r 

5. scan -a

Only Tape drives available but no robot show on 

6. Devfsadm -C ,

7. Do the step 5 , still the same problem 

8. I reboot the library, and do the the scan -a , it shows the robot 

9. tpconfig -d   # Still no show the robot 

10. I use the device wizard on NBU , to find the Robot, two tape drivers.

11. Check the robot , and device monitor, it able to see all 

12. Check the STU and robot , it shows that the NBU connect to Tape library.

13. Try to robot inventory, it able to work. 

14. Try to run the policy, the policy show mount the tape and begin writing. 

I will check it again tomorrow if there are backup successfully and update the status as well

Thank you for your recommendation 

Cheers,

[Mike_Gavrilov]

Tape Library replacement isn't a simple support task and sounds like a task for expirienced engineer's  because you need to consider many factors (NBU, Solaris, Tape Library HW). You've probably faced with the sg.conf issue because Taple Library relacemnet usually requires sg.conf re-cration procedure:

https://www.veritas.com/support/en_US/article.TECH71073

but you should be sure that you've already created backup stratagy and able to restore initial configuration _before_ you start generating sg.conf.