Description

Enterprise Vault 14.2 onwards, Elasticsearch is the new indexing engine. To move the indexes to an index location on a different index server, perform the following actions:

1. On the first index server, take a snapshot of the index data.
2. On the other index server, first, ensure that Enterprise Vault is freshly installed and configured, then restore the above-referenced snapshot of the index data.  Note that the restore location folder can contain other index data provided the drive has sufficient space available.

Resolution

1. Back up the SQL databases and the EV server.
2. Ensure both servers have the same index snapshot location configured.
   If the same index snapshot location is not configured on the other server, you must set that up by using the cmdlet Set-EVIndexSnapshotLocation. See the Enterprise Vault PowerShell Cmdlets guide for more information.
3. Restart the Enterprise Vault Indexing Service on both index servers.
4. Take the snapshot on the first index server by using the cmdlet New-EVIndexSnapshot. See the Enterprise Vault PowerShell Cmdlets guide for more information.
5. Stop the Enterprise Vault Indexing Service on the first index server.
6. Manually copy the index snapshot repository folder from the first index server to the index snapshot location configured on the other index server.
   The index snapshot repository folder path is displayed on the output for step 4 above.
   
   Determine the index snapshot location configured on the other index server by using the cmdlet  Get-EVIndexSnapshot. See the Enterprise Vault PowerShell Cmdlets guide for more information.
   
7. Restore the index snapshot on the other index server by using the cmdlet Restore-EVIndexSnapshot . See the Enterprise Vault PowerShell Cmdlets guide for more information.
8. Stop Enterprise Vault Indexing Service on the other index server where you have restored the index snapshot.

9. Update all the index volumes of the first index server to the other index server. Run the following SQL queries in SQL Server Management Studio:

   1. Determine the index location by running the following SQL query in SQL Server Management Studio:
      
      USE EnterpriseVaultDirectory
SELECT CE.ComputerName, CE.ComputerNameAlternate, IRP.IndexRootPathEntryID, IRP.IndexRootPath, ISE.ServiceEntryID, ISE.Description
FROM ComputerEntry CE, IndexingServiceEntry ISE, IndexRootPathEntry IRP
WHERE CE.ComputerEntryID = ISE.ComputerEntryID AND ISE.ServiceEntryID = IRP.IndexServiceEntryID
ORDER BY CE.ComputerName
      
      Make a note of the IndexRootPathEntryIDs for the old index root path and the new index root path.

   2. Update the index locations by running the following SQL query in SQL Server Management Studio:
      
      Note: 
      The old IndexRootPathEntryId should be replaced with the IndexRootPathEntryId value returned for the old index root path in step 9-1.
      The new IndexRootPathEntryId should be replaced with the IndexRootPathEntryId value returned for the new index root path in step 9-1.

      USE EnterpriseVaultDirectory
DECLARE @OrigIndexRootPathEntryId EVGUID
DECLARE @NewIndexRootPathEntryId EVGUID

      SET @OrigIndexRootPathEntryId = 'old IndexRootPathEntryId'
SET @NewIndexRootPathEntryId = 'new IndexRootPathEntryId'
      
      -- Update the index volumes to point at the new location
      
      UPDATE IndexVolume
SET IndexRootPathEntryId = @NewIndexRootPathEntryId
WHERE (IndexRootPathEntryId = @OrigIndexRootPathEntryId)

   3. Inform Enterprise Vault that it needs to update the paths of the volumes on the Enterprise Vault service startup by running the following SQL query in SQL Server Management Studio:
      
      UPDATE IndexingServiceEntry
SET IVSyncNeeded = 2
WHERE ServiceEntryId IN (SELECT IndexServiceEntryId FROM IndexRootPathEntry WHERE
IndexRootPathEntryId IN(@OrigIndexRootPathEntryId, @NewIndexRootPathEntryId))

10. Following completion of the SQL script, restart all the Enterprise Vault Services.

Note: When the Indexing Services start up, they will synchronize their respective index volume metadata; depending on the number of index volumes associated with the index root path relocation, this may take some time. The progress can be monitored in the Event Log.