tld is disabled and the tape drive is standalone

[hamzafayyaz1983]

Hi,

I was taking the backup of a san share directly to the tape library using NDMP.
Now i want to reconfigure my netbackup server using normal backups through backup server.

I have mounted the san share on a linux machine and now want to take the backup of the mounted directory through the backup server using netbackup.




now when i am reconfiguring my library to take backups through my backup server. i am getting the following error which is attached








Regards,
hamza

[Marianne]

Have you updated Device Mappings?
http://seer.entsupport.symantec.com/docs/351807.htm

[hamzafayyaz1983]

My scsi card was problematic and i got it replaced with the new one.
Now i can see the enteries in the /dev/rmt

My device mappings are update to dated. I have checked the version from

root@bkpsrv # /usr/openv/volmgr/bin/tpext -get_dev_mappings_ver
device mappings version in the EMM database is 1.66
device mappings version from the local file is 1.66
Local device mappings file is up-to-date

but i guess since i am reconfiguring it so the old enteries are still residing which needs to be removed.

[Har-D]

Hi,

Is this NBU 6.5.2 (or above)

As I can see from the snap, under "Devices > Robots", I believe, we have just this robot currently configured. No other devices are configured. Is it?
If yes, then the best is delete all devices from the EMM and then go for reconfigure with Wizard, as it will avoid creation of any orphan device entry.

To delete all devices :

# /usr/openv/netbackup/bin/admincmd/nbemmcmd -deletealldevices -allrecords
(** Thie command works NBU-6.5.2 or above)

[hamzafayyaz1983]

Hi,

I am using Netnackup server version 6.5 and yes Mr Har-D you have got it right.

I am facing the problem of devices acting as orphans coz all the old enteries are not deleted

but this command is not working in 6.5. can u tell me same command for 6.5.


Thanx
Hamza

[Kisad]

I had faced a somewhat similar issue. deleting and adding the robot manually from tpconfig worked for me. Try the following steps and see if that works.

**please note that i had tried to configure the robot from the GUI and also through tpautoconf -r but somehow those didnt work for me.


1.run tpconfig command and use the menu to delete the robot manually.
2.receycle netbackup daemons.
3.check if the robot is gone.it shoudnt be listed after the above steps are performed.
4.run tpconfig again and manually add the robot.
5.recycle netbackup deamons.

Good Luck

[Har-D]

Hi,

The above steps (as Kisad mentioned) are perfect if we don't have NBU > 6.5.2 .

However, if you can see the devices in output of tpconfig -d , you can also try :

tpconfig -multiple_delete -drive <drvindex1>:<drvindex2>    : For Drives.
tpconfig -multiple_delete -robot <robnum1>:<robnum2>     : For Robots

[hamzafayyaz1983]

Guys i have already  tried deleting with the tpconfig on the command line.

I have manually deleted both the tape drive and the robotic arm from the ./tpconfig

and then checked the robot and the tape in the gui and it wasnt there. then i rebooted the machine and


ran the wizard again and got the same error.


Will i add the robot first or the drive first while adding it manually



thanx
hamza

[Kisad]

Hi

please add the robot first ,recycle netbackup and check if its getting detecting. try doing a robtest ,it shouldnt give any errors. Once you are sure that the robot is configured  then please proceed to add the drives.once again recycle netbackup daemons and verify the drives are configured properly.

also please make a note that the deamons tlddd and tldcd are running ,these are needed for the robot to work.

[Har-D]

Hello Hamza,

Could you please copy the following outputs from the Linux master :

1. # cat /proc/scsi/scsi

2. # /usr/openv/volmgr/bin/scan

3. # /usr/openv/volmgr/bin/tpautoconf -t

4. # ll /dev/*st*

5. # lsmod | egrep '^sg|^st'

Also, what is the falvor, release and kernel version of linux?

[Marianne]

Seems your Device Mappings is NOT up to date.
The link that I've posted is for 1.89:

Veritas NetBackup (tm) Server / Enterprise Server 6.x and 7.x Device Mappings Package for UNIX / Linux 1.89

Your version is 1.66.

Please confirm that download was successful (maybe retry the download) and retry the steps in the TechNote to install the device mappings.

[Marianne]

I have just downloaded and updated device mappings in our lab:

-rw-r--r-- 1 root root 135168 Jul 9 12:37 Mappings_6_351807.tar
root@v240-2 # tar xvf Mappings_6_351807.tar
x Readme.txt, 4925 bytes, 10 tape blocks
x external_types.txt, 125054 bytes, 245 tape blocks
x external_robotics.txt, 1740 bytes, 4 tape blocks
root@v240-2 # cp external_types.txt /usr/openv/var/global/
root@v240-2 # cp external_robotics.txt /usr/openv/var/global/
root@v240-2 # tpext -loadEMM

(Used cluster to stop/start NBU)

root@v240-2 # tpext -get_dev_mappings_ver
device mappings version in the EMM database is 1.89
device mappings version from the local file is 1.89
Local device mappings file is up-to-date