03-26-2012 11:15 PM
Hi all,
I have a scenario, the " ltid " process is going down often on my media server.
Details:
Master Server OS: Solaris
Media server OS : Windows 2003 R2
Netbackup Version(Master & Media) : 7.0
Any suggessions on fine tuning?
Solved! Go to Solution.
03-27-2012 06:22 AM
A few other things to check:
1. The Removable Storage Service should be stopped and disabled to prevent Windows taking the robot and drives away from NetBackup
2. The Medium changer should not have specific drivers loded - it should just be seen as an unknown medium changer
3. For the tape drives ensure you have the AutoRun key set to 0 for the tape drivers - see this tech note:
03-27-2012 12:02 AM
How often is it going down.
Did this every work, what has changed on the system to cause it to break ?
Please post the ltid log for us to look at.
/usr/openv/volmgr/debug/ltid
Martin
03-27-2012 12:10 AM
If log folders do not exist on the media server, first create the debug folder under <install-path>\veritas\volmgr. Then create ltid folder under debug.
Please also add the following entries in <install-path>\veritas\volmgr\vm.conf:
VERBOSE
DAYS_TO_KEEP_LOGS = 3
Restart NetBackup Device Manager service after creating folders and adding entries to vm.conf.
Check ltid log as well as Event Viewer Application and System logs for errors.
03-27-2012 01:18 AM
Hi Martin & Marianne,
Thanks for your reply. litd is going down twice or thrice a day inconsistantly, some times running perfectly fine for the whole day.
Below are the brif log error message, were in the higlighted are often repeated in the" ltid" log file.
I have also find a tech note on this issue, stating this is a bug on Media and Device selection (MDS).below are the links. Kindly assist.
http://www.symantec.com/business/support/index?page=content&id=TECH16248
03-27-2012 02:55 AM
Good find on the technote, but ...
Looking at the EEB, the issue has only been seen on Linux (only a Linux EEB available)., but, that does NOT mean it couldn't affect Windows - just that it hasn't been seen yet.
However, the fix has gone into NBU 6.5.6 and above - they may have made the code change across all versions, even though the issue seems only to have been seen on Linux (far as I can tell).
Also, you do not say if you are using multiplathing ???
Are youusing NIC 'teaming' - This has been known to cause this issue ?
I'm thinking that you might have to log a call on this one, to investigate the 'possibility' of a connection with the EEB.
Thanks,
Martin
03-27-2012 06:22 AM
A few other things to check:
1. The Removable Storage Service should be stopped and disabled to prevent Windows taking the robot and drives away from NetBackup
2. The Medium changer should not have specific drivers loded - it should just be seen as an unknown medium changer
3. For the tape drives ensure you have the AutoRun key set to 0 for the tape drivers - see this tech note:
03-27-2012 07:30 AM
Martin,
Yes, they are assigned to dedicated backup NIC teaming.
03-27-2012 07:33 AM
Hi Mark,
Yes, I suspected the same, checking as stated and will let you know if it helped me in resolving this issue.
Thanks.