how to change NetBackup NDMP drive path after drive/datamover relationship has changed?

[tythecellist]

Earlier today I re-zoned drives in my tape library to optimize configuration and distribution.  The new addresses seen by the NAS datamover are below.

[nasadmin@XXXXX-0186 ~]$ server_devconfig server_2 -l -s -n
server_2 :
               Scsi Device Table
name                addr         type  info
0186_12113_dr1      c176t0l1     tape  IBM ULTRIUM-TD5 G9N4
0186_12113_dr2      c176t0l2     tape  IBM ULTRIUM-TD5 G9N4
0186_12114_dr1      c208t0l0     tape  IBM ULTRIUM-TD5 G9N4
0186_12114_dr2      c208t0l1     tape  IBM ULTRIUM-TD5 G9N4
0186_12115_dr1      c224t0l0     tape  IBM ULTRIUM-TD5 G9N4
0186_12115_dr2      c224t0l1     tape  IBM ULTRIUM-TD5 G9N4
0186_13113_dr1      c256t0l0     tape  IBM ULTRIUM-TD5 G9N4
0186_13113_dr2      c256t0l1     tape  IBM ULTRIUM-TD5 G9N4
gk01                c0t0l0       disk  1 053107000020APM00114700186
gk161               c16t1l1      disk   0531010011000APM00114700186
0186_11115_dr1      c128t0l1     tape  IBM ULTRIUM-TD5 G9N4
0186_11115_dr2      c128t0l2     tape  IBM ULTRIUM-TD5 G9N4


[nasadmin@XXXXX-0186 ~]$

My question is this:  what procedure should I be looking for in the Admin guides to make my RHEL NetBackup master and media servers aware of the new addresses so that they, and the drives seen by the datamover, are aligned?  I'm seeing NetBackup attempt to load tapes into devices that aren't addressable as configured.   I've looked all over the place in the NDMP and other manuals but not found the right information.

Thanks

[Marianne · Accepted solution]

Easiest will be to delete the existing drive config in NBU, restart ltid on the media server, and then config from start (as if new config).

[Genericus]

I agree. 

In fact, I have found that having a script on the master or media hosting them, with the command line to update the drives can be very handy.

Heck, I pretty much capture every procedure I do, so I have a reference of the commands I need to enter.

If I do it a lot, I set up a script and an alias. 

Work smarter, not harder.

[tythecellist]

Thank you Marianne!   I did exactly that and my issue is now resolved.  (We'd found that the configuration setup by a previous admin, who'd since left the company, was undocumented and not functioning well, so clean-up and documentation was in order.)  

Essentially, to rebuild the device paths, we did this:

1. Run ‘/usr/openv/netbackup/bin/admincmd/nbemmcmd -deletealldevices -machinename server_name -machinetype media’.  You’ll need to modify the ‘server_name’
2. Run tpconfig -d on the Media Server and confirm that the command has completed and we should no longer have any devices configured.
3. Run the device configuration wizard to configure the regular non-NDMP drives associated with the Media Server
4. Refresh the GUI / Run tpconfig -d and verify you’re seeing the correct non-NDMP drives.
5. Run the device configuration wizard again, this time you’ll need to highlight the media server, then click the change button in the upper right, and choose NDMP, then finish going through the wizard.
6. Refresh the GUI / Run tpconfig -d again to verify you’re seeing the correct NDMP device paths.