You still need to create the log directory (unless it's been done before) :
<install path>\Veritas\Volmgr\debug\ltid\

Then turn up the media server's logging level via the Admin Console
under Host Properties. I think 5 is maximum logging. Then keep an eye
on disk space on the media server!



On Wed, 2 Mar 2005 18:08:30 -0600, Karen Grider <karen.grider AT fedex DOT com> 
wrote:
>  
>  
> 
> Windows environment .  NB 5.1    Should my san media servers have a vm.conf?
> 
>   
> 
>   
>  
> 
> Karen F. Grider 
> 
> Sr. Business Systems Analyst 
> 
> EBS Hosting 
> 
> 901-434-9193 
> 
> karen.grider AT fedex DOT com 
> 
>  
>  
> 
>   
> 
> -----Original Message-----
>  From: Karen Grider 
>  Sent: Wednesday, March 02, 2005 4:54 PM
>  To: 'veritas-bu AT mailman.eng.auburn DOT edu'
>  Subject: Window ltid service problems 
> 
>   
> 
> I have a windows media server running Netbackup Enterprise server 5.1 mp1. 
> I have seen this on several of my media servers and on my master at one time
> or another.   
> 
>   
> 
> I bring down Netbackup and when I bring my services back up and run vmoprcmd
> (or any service that uses or refers to the device manager) I get the error
> "ltid is not active".  I confirm that it is active.  Sometimes I wait 15 or
> so minutes and the error goes away.   Has anyone seen this before or know
> how to fix this problem? 
> 
>   
> 
> Karen F. Grider 
> 
> Sr. Business Systems Analyst 
> 
> FedEx Express EBS Hosting 
> 
> karen.grider AT fedex DOT com 
> 
>   
> 
>