indexing

5 Topics

index upgrade from 32bit to 64bit
Hi All, I have a customer running EV 11 and currently in the process of planning upgrade to EV 12. There are still some 32bit indexes that are yet to complete conversion to 64bit due to large number of 32bit indexes. Can the index upgrade (32 to 64) be resumed after performing the upgrade to EV 12? Is it mandatory to upgrade 32bit index to 64 prior to upgrade to EV 12? Thanks! Regards, VJ
Solved
vjose790
5 years ago Place Enterprise Vault
936Views
0likes
1Comment
High Index Volume count causes indexing service to not become fully functional
I need some advice with a high load indexing server. One of our Indexing server is managing indexes for 7 vault stores. The index volume count on this server is over 150000. So if the index service restarts, it doesnt become fuly functional until the volumes are synchronized. Any everytime thevolume sync just stop after a certain point and 41376 events repeats the same nummber without the indexing service becoming fully functional. One option we have considered is to move half index locations from high load server to a different server from SQL server. Is this a viable option?If anyone has any other suggestions, please do share!
OldEmployee
7 years ago Place Enterprise Vault
811Views
0likes
2Comments
Versioninfo.xml missing
OK, I migrated an EV11.0.x to 12.0 So far so good, DB were upgraded without any problem. Services started normally but, at one, the indexing stopped. Looking further in the event viewer I saw this An unexpected error has occurred. Error Summary: Indexing Service start up error Error Details: Could not find file 'C:\Program Files (x86)\Enterprise Vault\EVIndexing\data\InitialConfigurationData\indexmetadata\VersionInfo.xml'. Reference: ServiceBaseEx::Run Stack Trace: at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.File.InternalCopy(String sourceFileName, String destFileName, Boolean overwrite, Boolean checkHost) at System.IO.FileInfo.CopyTo(String destFileName, Boolean overwrite) at Symantec.EnterpriseVault.Indexing.Admin.IVMetadataLocationUpdater.UpdateVersionInfoFile(String metaDataPath) at Symantec.EnterpriseVault.Indexing.Admin.IndexAdminService.OnPerformStartup(Boolean HotRestart) at KVS.EnterpriseVault.Common.ServiceBaseEx.Run() For more information, see Help and Support Center at http://telemetry.community.veritas.com/entt?product=ev&language=english&version=12.0.0.0&build=12.0.0.1528&error=V-437-41293 I di try to copy the versioninfo.xml from the old to the new server. No can do. the file is deleted when the indexing service start. Idea how to resolve this? Cheers, Olivier
The_Boulon
7 years ago Place Enterprise Vault
1.7KViews
0likes
3Comments
Updating existing index location with data
So I understand that when adding a new Index location, the location should empty. However, we will be migrating indexes to a different NetApp Filer. So the path for the indexes will change. During this migration the indexes will be copied to the new location and only after that we will get the new paths. In this case, we wont be able to add the Index location as it already has data in it and wont be able to update the SQL entries as per: https://www.veritas.com/support/en_US/article.HOWTO59084 Is it possible to update these entries after the data is copied or do we have to update the new path before the copy starts.
Solved
OldEmployee
8 years ago Place Enterprise Vault
1.6KViews
0likes
8Comments
Index Rebuild subtask failing with Error 41352
We had a volume that showed up in a failed state. A verification did not complete successfully. We then proceeded to try a volume rebuild. Each time the rebuild fails with an event in the EV event log: The processing of the Rebuild Sub task has stopped following errors. Archive name:(removed) Task: Rebuild_2017-10-16_09:35:57_PM Rebuild Sub task ID: 1E53DADB142C3A344B6B7DACD574076491110000ent-vault-site_1904 Reason: ContentSource Error Type: NonCritical Description: Failed to delete Index Volume: [1E53DADB142C3A344B6B7DACD574076491110000ent-vault-site]. For more information, see Help and Support Center at http://entced.symantec.com/entt?product=ev&language=english&version=10.0.4.0&build=10.0.4.1189&error=V-437-41352 I can't seem to find any reason that the system cannot delete the Index Volume. Would love to hear any suggestions
stullier
8 years ago Place Enterprise Vault
1.3KViews
0likes
3Comments