Indexing does not get performed on replica server in EngageOne Vault

Issue

EngageOne Vault mirroring process compares the files and copies the missing files from Master to the replica server.  However, it doesn't index the newly replicated files. Index files are remaining in the process directory, and don't get indexed unless an e2loaderd process on the replica EngageOne Vault server is restarted.

Cause

  • The loader was in the process of trying to find files to mirror and had not finished comparing. The e2loaderd INI file has months set to -1 which means it tries to mirror everything.
    e2loaderd.ini:
    
    [Mirror1]
    enable=1
    months=-1
  • The default mirror 'maxfind' block is probably too small.

Resolution

UPDATED: January 22, 2020
  • Change the month's parameter value to 1 which only checks one-month files.
  • Increase the 'maxfind' block size.
    e2loaderd.ini:
    
    [Mirror1]
    maxfind=512