This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(115.19999999999999, 35%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EP%3C/text%3E%3C/svg%3E)
Hi,
Does anyone know why New-SPEnterpriseSearchIndexComponent toghether with -RootDirectory does not change all index files location? At least most of file are being moved to the provided location but still some of file are processing in 'C:\Program Files\Microsoft Office Servers\16.0\Data\Office Server\Applications'.
After location for index is changed and I'm executing (Get-SPEnterpriseSearchServiceInstance).components I can see this
PS C:\Users\user> (Get-SPEnterpriseSearchServiceInstance).components
Id : 3009aa8a-4f1a-49e2-98aa-289d69a0f6fd
ServerName : XXXXXXXXX
IndexLocation : E:\SPIndex
State : Ready
DesiredState : Ready
IndexLocation : C:\Program Files\Microsoft Office Servers\16.0\Data\Office Server\Applications
Initialized : True
Name : 9235f889-3352-40ed-b44d-3118ec467b04
ServerName : XXXXXXXX
ServerId : 82840937-6e43-4b00-a986-ed7c96e0eeb9
Server : SearchServiceInstance
Does anyone know why there are still some files processed in the default location? Maybe (for any reason) some files have to remain in the default location? Is it possible to change all "Index locations" to the custom directory?
Thanks in advance
Would you like to provide your whole process? New-SPEnterpriseSearchIndexComponent only creates a new index component. It does not remove the index component. Have a check with Get-SPEnterpriseSearchStatus, it will shows the status of all the search components. If you can find the old index component, it means you did not remove the old Index component, which you need to do.
Have a check on this article which provides the whole process of moving index component: https://www.totalsol.com/how-to-move-a-sharepoint-search-index/
Unless you install SharePoint Server to an alternate volume, the behavior you're seeing is expected. You can move the Search Index, but not other files that are still processed in that location.
Thank you both for reply
@Jerry Xu-MSFT I already checked and all inactive topologies are removed, therefore this is not the case
@Trevor Seward Are there any special requirements - in regards to files in this location - for search/index backup-restore scenario (backup-restore other than native SharePoint)? The files have to be restored from exactly the same timestamp as index?
in addition I can tell you that I've installed SharePoint using config.xml file and this file contained
<Setting Id="DATADIR" Value="E:\Program Files\" />
so all binaries should be placed on E drive but as we see they aren't....
can you advice about a 'custom backup' strategy in this case? The files from 'C:\Program Files\Microsoft Office Servers\16.0\Data\Office Server\Applications' have to be restored from exactly the same timestamp as index files?