The Rebuild wizard lets you rebuild index volumes and upgrades any 32-bit index volumes it encounters.

The Rebuild starts by putting the original volume(s) into read-only mode. A new, hidden, volume is then created and items start to be added to it. Whilst data is being ingested, progress of the rebuild and details of any failed items will be recorded in the report.

The old index volume(s) remain searchable during the rebuild to avoid impact on users.

If indexing is distributed across a group of servers, the Rebuild task will run on the server that’s been chosen to host the new index volume.

Once the rebuild has completed successfully, the old index volume will be replaced with the new volume, which at that point becomes searchable. The old volume(s) will be deleted.

To troubleshoot or monitor the progress of a running Rebuild, use Dtrace to monitor the following processes:

• EVIndexAdminService.exe
• EVIndexVolumesProcessor.exe
• StorageCrawler.exe

Note: The rebuild process will only add previously converted content to the index. If content conversion of an item type was excluded or bypassed the item must be re-archived in order to ensure all content can be processed for conversion.  The file type must not exist in the exclusions list or have conversion bypassed when being re-processed.  

 

You want to troubleshoot or monitor an index rebuild.