Link to home
Start Free TrialLog in
Avatar of npdodge
npdodge

asked on

Is it safe to delete old Exchange 2013 content index files?

I have a number of old .merge folders in the \ms\%default folders of my Exchange 2013 DAG members that haven't been modified in over 3 months and is taking up over 120GB.  Only 2 out of the 5 databases have these older .merge folders and just happen to contain public folder mailboxes if that makes a difference.  We are running Exchange 2013 CU 20.  Is there something I can run to determine if it's safe to delete these?
ASKER CERTIFIED SOLUTION
Avatar of Sunil Chauhan
Sunil Chauhan
Flag of India image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of npdodge
npdodge

ASKER

Thanks but the article you suggested does not apply to DAGs.
That would be similar, as an additional step, you would just need to reseed the Catalog only..

so rebuild the content index on the primary DB and then reseed.

Reseed the content index catalog from a specific source
This example reseeds the content index catalog for the database copy DB1 on Mailbox server MBX1 from Mailbox server MBX2, which also has a copy of the database.

Update-MailboxDatabaseCopy -Identity DB1\MBX1 -SourceServer MBX2 -CatalogOnly

https://technet.microsoft.com/en-us/library/ee633475(v=exchg.150).aspx
Avatar of npdodge

ASKER

I have an issue with just one database and these .merge files are large and outdated on the server it's currently active on and also on another DAG member that is passive.  Should I stop the Exchange Search Service on both DAG members and delete the GUID named folders on both or should I just do it on the one DAG member that is currently hosting the active database and reseed to the other.  My question is will reseeding remove all of the old and corrupt data in the GUID named folder on the passive DAG member?

Right now these are the steps I've documented for the process.  Please let me know if anything needs to be corrected.  My active DAG member is MAIL02 and passive DAG member is MAIL01.

1.      Stop Exchange Search Service and Microsoft Exchange Search Host Controller on MAIL02 (https://technet.microsoft.com/en-us/library/ee633475(v=exchg.150).aspx says that the Microsoft Exchange Search Host Controller also needs to be stopped)
2.      Delete D:\Microsoft Exchange\DB_PF\8771B6F0-602F-419F-A51F-65F62904C42112.4.Single on MAIL02
3.      Start the Exchange Search Service and Microsoft Exchange Search Host Controller on MAIL02
4.      Run “Get-MailboxDatabaseCopyStatus -Server MAIL02 | ft -auto” and verify that DB_PF is crawling
5.      Add MSExchange Search IndexesCrawler: Mailboxes Remaining counter to perfmon and wait until it reaches 0
6.      Reseed to other DAG member with the following command:  Update-MailboxDatabaseCopy -Identity DB_PF\MAIL01 -SourceServer MAIL02 -CatalogOnly
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.

I have recommended this question be closed as follows:

Accept: 'Sunil Chauhan' (https:#a42637803)

If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.

seth2740
Experts-Exchange Cleanup Volunteer