05-02-2016 01:08 AM
Hi All,
If we see this then we need to restart ltid service to resolve this issue.
Can anyone suggest which logs we need to read to find out the root cause or when incident happened.
I checked /usr/openv/volmgr/debug, /usr/openv/netbackup/logs/bptm and system logs.
Can anybody suggest on this.
Solved! Go to Solution.
05-02-2016 11:14 PM
The only reason I know of that they show restart is when something changes in the configeration.
volmgr/debug/tpcommand might show something but it would depend if it was set up at the time.
05-02-2016 11:14 PM
The only reason I know of that they show restart is when something changes in the configeration.
volmgr/debug/tpcommand might show something but it would depend if it was set up at the time.
06-12-2016 11:32 PM
Yeah I checked it but did not find anything. Also there was not any configuration change.
06-12-2016 11:49 PM
It's been 6 weeks since you posted here!
Have you restarted NBU yet?
Have you enabled logs as suggested by Martin on 3 May?
Anything in OS System log or NBU logs?
Important that you troubleshoot at the time when the issue is seen....,
06-13-2016 01:41 AM
I am not sure which logs track it, but i have seen generally this appears, when you reconfigure tape drives on you rmedia server and don't restart LTID to get the new configuration.
to refresh the configuration we have to restart the LTID.
06-13-2016 11:51 AM
06-16-2016 03:13 AM
volmgr/debug/tpcommand