Creating new indexes on a secondary server in EngageOne Vault

Takes a large amount of time to do reindex in EngageOne Vault. This can be advantageous to do this on another server, and then promote the changes to the production server. 
  1. Stop EngageOne vault services in the vault testing environment\Secondary server.
  2. Ensure that the testing environment has the same version of EngaGeOne Vault as a production environment.
  3. Ensure that the testing environment has the same database.ini /profiles.ini settings as a production environment.
  4. Ensure that the following vault directories on the testing environment are empty: 
  5. Copy all of the DRD files from production vault/server/docdata to the testing environment vault/server/docdata.
  6. In the testing, the environment creates a copy of each DRD file, but instead of the.DRD extension, give it a .index  extension.  For example: copy *.drd *.index
  7. Move the newly created .index files from step 5 to the vault/server/process directory
  8. Start EngageOne vault services in the testing environment. Monitor the e2loaderd log and wait for the reindexing to be complete.

 Post reindexing completion, copy new indexes to the production environment as follows:

  1. Stop EngageOne vault services on the production server.
  2. Rename the production vault index directory from 'index' to 'old.index'
  3. Copy index directory from a testing environment to a production environment
  4. Start EngageOne vault services and test.  
Note: If any new files ingested in the production server since the index is created in a test\UAT environment, need to manually INDEX those files in the production environment to be viewable in production.
UPDATED:  December 23, 2019