'IVMetaDataSync' returns a count of search collections as '-1' thus Indexing meta data synch never completes.

'IVMetaDataSync' returns a count of search collections as '-1' thus Indexing meta data synch never completes.

Article: 100015196
Last Published: 2015-06-04
Ratings: 0 0
Product(s): Enterprise Vault

Problem

Enterprise vault Indexing service performs Meta Data Consistency check & compare search-collection with Directory database Index volumes. Most of time the comparison is equal in healthy environment so meta data synch does not initiate during service start.

In rare circumstances the search-collection folders may get corrupt OR missing, Enterprise vault indexing have self-healing capabilities that fix corrupt / missing search-collection automatically during startup of Indexing service, In those situation the meta data synch starts against only corrupt/missing search-collection folders. Followings lines can be seen in the d-trace of EVIndexAdminService process.

EV-L           {IVMETADATASYNC.EN_US} Checking if index volume metadata synchronisation is required.
EV-L           {VELOCITYINDEXINGENGINE.EN_US} Getting index volume count started
EV-L           {IVMETADATASYNC.EN_US} Index volume count from indexing engine metadata: [4]. Index volume count in Directory database: [6]
EV-L           {IVMETADATASYNC.EN_US} Index volume metadata and repository are out of sync. Forcing index volume synchronization.
EV-L           {IVMETADATASYNC.EN_US} Index volume metadata synchronisation [is] required.
EV~I           |Event ID: 41372 Indexing Service has started the synchronization of index volume metadata between the indexing engine repository and the Directory database.

Error Message

In certain environment, due to high level of inconsistency, 'IVMetaDataSync' returns the count of search collection as '-1' thus Meta data attempt to clean inconsistency during every time start of EV indexing service and never completes.  Followings lines can be seen in the d-trace of EVIndexAdminService process.

EV-L           {IVMETADATASYNC.EN_US} Checking if index volume metadata synchronisation is required.
EV-L                    {VELOCITYINDEXINGENGINE.EN_US} Getting index volume count started
EV-L                    {VELOCITYINDEXINGENGINE.EN_US} Discovered localy stored index data for index volume 121A5CA269FC78047B7D4940675F80A40_16257. Excluding from total count of index volumes and renaming local index data.
EV-H                    {VELOCITYINDEXINGENGINE.EN_US} Exception: Cannot create a file when that file already exists.| Info: Diag: Type:System.IO.IOException ST:   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)|   at System.IO.Directory.Move(String sourceDirName, String destDirName)|   at
Symantec.EnterpriseVault.Indexing.IndexingEngine.VelocityIndexingEngine.GetIndex VolumeCount(String metadataPath) Inner:None
EV-L                    {VELOCITYINDEXINGENGINE.EN_US} Getting index volume count completed
EV-L            {IVMETADATASYNC.EN_US} Index volume count from indexing engine metadata: [-1]. Index volume count in Directory database: [6]
EV-L            {IVMETADATASYNC.EN_US} Index volume metadata and repository are out of sync. Forcing index volume synchronization.
EV-L            {IVMETADATASYNC.EN_US} Index volume metadata synchronisation [is] required.
EV~I            |Event ID: 41372 Indexing Service has started the synchronization of index volume metadata between the indexing engine repository and the Directory database.
 

Cause

Indexing Engine copies & rename 'Crawl1' to 'Crawl1.old' inside affected search-collection folder. During startup of indexing tries to repeat same then fails with exception as 'Crawl1.old' already exist.

Workaround:-

Recreate Indexing Metadata by following steps:-

A. Stop Enterprise Vault Indexing service OR Indexing Resource in case of Cluster.
B. Rename OR Delete Indexing MetaData.
c. Start Enterprise Vault Indexing Service OR Indexing Resource that will re synchronize Indexing metadata.

Note: This re synchronization process can take an extended amount of time depending on the number of index volumes (collections) managed by the indexing service. Once the metadata synchronization process is completed then indexing service will become fully functional.
 

Solution

This issue has been addressed in the following release:

Enterprise Vault 11.0.1 Cumulative Hotfix 2 Release
https://www.veritas.com/docs/000025301

Enterprise Vault 12 release
https://www.veritas.com/docs/000099905
Note: For information on how to obtain Enterprise Vault 12 see: How to obtain the license key and installation download for Veritas products

 

Was this content helpful?