Robot stopped working with 'ltid Robot TLD(0) is not active on this machine' in syslog

[List_Man]

Hi all,

We had a curious problem last night with a robot that put itself offline after having done tests to write files to a nfs disk.

The message that appeared in /var/log/syslog was:

'ltid Robot TLD(0) is not active on this machine'

After that all policies exited with status 6 waiting for a tape to be mounted.

Have to say that we did some heavy performance tests to a NFS disk that is also being accessed by Netbackup as another storage medium (backup to disk), not being the robot. For if it matters: we did also a unmount/mount of this disk to change the block size for writing/reading.

Any suggestions are welcome.


We have Netbackup 5.1 on Redhat 2.6.9-5.ELsmp

[Abesama]

Did you try knowledgebase search on the Symantec support web page?
http://www.symantec.com/business/support/overview.jsp?pid=15143

NBU5.1 does not have EMM, it will not activate/deactivate the robots and tape drives individually ... strange.

Try robtest, check if you can see the robot path from the OS (cat /proc/scsi/scsi) and do scan (/usr/openv/volmgr/bin/scan)

What's the exact message syntax in syslog ... any other messages in there?

Also, try stop NBU services, make sure everything's gone (bpps -a) and start vmd (/usr/openv/volmgr/bin/vmctrldbm -i) and start ltid (/usr/openv/volmgr/bin/ltid -v) and check out the syslog again.

Abe