cancel
Showing results for 
Search instead for 
Did you mean: 

ltid is often going down on media server.

Raghavendran_Lo
Level 2
Certified

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?

1 ACCEPTED SOLUTION

Accepted Solutions

Mark_Solutions
Level 6
Partner Accredited Certified

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:

http://support.microsoft.com/kb/842411

View solution in original post

7 REPLIES 7

mph999
Level 6
Employee Accredited

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

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

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.

Raghavendran_Lo
Level 2
Certified

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.

https://www.symantec.com/business/support/index?page=content&pmv=print&impressions=&viewlocale=&id=T...

 

http://www.symantec.com/business/support/index?page=content&id=TECH16248

 

 

01:08:18.961 [261456.265660] <16> emmlib_SetDriveStatus: (0) SetDriveStatus failed, emmError = 2005004, nbError = 0
01:08:18.961 [261456.265660] <16> OprGeneralDevicePath: (-) Translating EMM_ERROR_DriveAlreadyAllocated(2005004) to 258 in the device management context
 
 
01:23:00.378 [261456.265660] <16> emmlib_SetDriveStatus: (0) SetDriveStatus failed, emmError = 2005004, nbError = 0
01:23:00.378 [261456.265660] <16> OprGeneralDevicePath: (-) Translating EMM_ERROR_DriveAlreadyAllocated(2005004) to 258 in the device management context
 
 
23:57:11.110 [305528.362500] <16> emmlib_SetRobotStatus: (0) The parameter RobotPath is empty... assuming we are setting robot state
23:57:11.110 [305528.362500] <16> emmlib_SetRobotStatus: (0) Host < toroondc12d >, RobNum < 0 >, RobotStatus < 1 >
23:57:11.110 [305528.362500] <16> emmlib_SetRobotStatus: (0) NdmpHost <  >
23:57:11.157 [305528.362500] <16> RobotConnect: Updated robot
 
 
22:36:39.376 [305528.362500] <16> auto_correct_robot_paths: Processing robot number 1 with serial number 9517970000, currently at path {2,0,9,0}
22:36:39.704 [305528.362500] <4> InitLtidDeviceInfo: Found 2 robots
22:36:39.720 [305528.362500] <4> get_changer_path: SCSI coordinates {2,0,9,0}, dos_path \\.\Changer0, pnp_path \\?\scsi#changer&ven_stk&prod_l180&rev_0306#4&2b19024e&0&000900#{53f56310-b6bf-11d0-94f2-00a0c91efb8b}
22:36:40.954 [305528.362500] <16> GetChangerGUIDRSM: Failed to open NTMS session
22:36:40.954 [305528.362500] <16> GetChangerGUIDRSM: Class not registered
 
Regards,
Raghav

mph999
Level 6
Employee Accredited

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

Mark_Solutions
Level 6
Partner Accredited Certified

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:

http://support.microsoft.com/kb/842411

Raghavendran_Lo
Level 2
Certified

Martin,

Yes, they are assigned to dedicated backup NIC teaming. 

Raghavendran_Lo
Level 2
Certified

Hi Mark,

Yes, I suspected the same, checking as stated and will let you know if it helped me in resolving this issue.

Thanks.