Exchange 2010 Log Folder Contents
Couple of questions. Exchange 2010 SP1 DAG. I have not been able to get a seed completed. Always fails on a missing .ci file. So I removed the MB copy today wanted to run a backup and clean out the logs. 1 - I noticed on my active mailbox copy in the Store log folder that there is a temp.edb (8MB) - is this normally there? It is not my production edb. 2 - There were three folders in there Ignored Logs, incseedInspect, and inspector - I know there are normal on the passive side, but should they also be on the active node? If not can I delete them? If they are needed the next time I re-create the DB copy they should be created, right? Thanks -SJMP Thanks,
April 12th, 2011 3:40pm

Hi The temp.edb file is used as temporary storage during the processing of transactions. About the directories leave them where they are. About the seed issue, it looks like there is something wrong with the Content Indexing files on the source database. You might try to recreate them using the following procedure: stop the Microsoft Search service remove the catalog directory start the Microsoft Search service For detailed steps see this blog: http://msexchangegeek.com/2009/09/09/how-to-manually-rebuild-the-full-text-index-catalog/ But does the seed completely fail or only the catalog part? If the last one is the case try to update the catalog only using this cmdlet: Update-MailboxDatabaseCopy -Identity DB1\MBX1 -CatalogOnly Regards, Johan Exchange-blog: www.johanveldh
Free Windows Admin Tool Kit Click here and download it now
April 12th, 2011 4:54pm

Hi SJMP, The temp.edb file is a temporary workspace for processing transcation. it is used to verify the queue database schema when the Microsoft Exchange Transport service starts. Although it isn’t a transaction log file, it’s kept in the same location as the transaction log files. For your seed issue, please help me to collect the following information: 1. What is the exact error you got, could you paste it in your next post? 2. Is there any related information in your event log? We need more information to confirm your problem. If this is something wrong with the Content Indexing file on the source database, I suggest you follow Johan’ suggestion to have a try. Thanks, Evan Liu TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
April 13th, 2011 11:04pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics