Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Syslog Error.

Created: 10 Jul 2013 • Updated: 13 Jul 2013 | 5 comments
mansoor.sheik's picture
This issue has been solved. See solution.

Hi all,

Got below error in master server syslog.

Symantec Authentication: Read error on /usr/openv/volmgr/misc/robotic_db/TLD0: Error(0)

can anyone suggest?

Operating Systems:

Comments 5 CommentsJump to latest comment

RamNagalla's picture

looks like TLD0 robot is not having good communication with Netbackup

did you see any operationnal issues..? drvies AVR mode? Q jobs.. ? backup failures?

can you do you robtest for TLD0 from contorl host and see what its returning..?

Marianne's picture

You need to tell us more about the environment:

NBU version and patch level first of all.

Authentication/Authorization seems to be configured. Is this right?

The error says that someone/some system tried to access the robot config. Nothing more.

With NBU 7.0.1 and later the Auditing feature can be configured to report on changes and activitities - VERY limited reporting in NBU 7.0.1 and more in 7.1 and later. 
Auditing is covered in NBU Admin Guide I.
 

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

mansoor.sheik's picture

Hi,

Master Server: HPUX

Version:7.1.0.2

NABC:Reconfigured. Symantec team has taken webex and done the same.

The error says that someone/some system tried to access the robot config. Nothing more.---- NBAC and second Tape Library configuration was done recently.

Will read the Admin guide and update you.

Marianne's picture

NBAC and second Tape Library configuration was done recently.

That would explain the message, right?

Auditing in version 7.1.x works best with OpsCenter to report on changes.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

SOLUTION
mansoor.sheik's picture

Hi Marianne,

Thanks for your suggestion. I have closed the syslog ticket.