How to bypass Server Settings Migration Wizard Index Verification check

Problem

Server Settings Migration Wizard stops at index location verification while importing packages onto a destination Enterprise Vault (EV) server.

Error Message

Path_To_Index_Location\Indexing is not a valid Index Root Path folder.

Cause

This issue can be seen when IndexVolume table from EnterpriseVaultDirectory database has entries for folders that are not present on the target storage where Indexes are stored for various reasons.

Solution

If there are a few Index Volume folders missing then, perform the below steps as a workaround:

1. Click Display Log File.

2. Check for Missing Index Sub Directory and note down the folder name with its path. (1F21C948A6B837A4A8FCE0C232A65A7F71110000ENTERPRISEVAULT)

9/22/2819    1:54:14 AM   Get index locations accessed by the export server starts ...
9/22/2819    1:54:14 AM   Get index locations accessed by the export server ends .
9/22/2819    1:54:14 AM   Missing Index Sub Directory [D: \Program Files\Enterprise Vault\Indexing\1F21C948A6B837A4A8FCE0C232A65A7F71110000ENTERPRISEVAULT]
9/22/2819    1:54:14 AM   D: \Program Files\Enterprise Vault\lndexing is not a valid Index Root Path folder.
9/22/2819    1:54:14 AM   D: \Program Files\Enterprise Vault is not a valid Index Root Path folder.

3. Copy the folder from the source or create the folder under Sub Directory with the name (1F21C948A6B837A4A8FCE0C232A65A7F71110000ENTERPRISEVAULT) mentioned in log.
4. Open the created Index Volume folder and create the DAT file according to Index Volume type (32 bit or 64 bit).
   1. For 32 bit Index Volumes create "Ind*/state.dat" file.
   2. For 64 bit Index Volumes create "state.dat" file.
5. Follow the same steps to create all missing Index Volume folders with DAT files and click Retry Verification.

Note: To remove stale entries from SQL server please contact Veritas Technical support.