Intermittent index issue and Clear-IndexLocationBackupMode
Hi Longtime listener, first time poster. We're currently running EV 12.1 on 4 servers (2x storage/task and 2x Indexing). Found that in the past 2-3 weeks, get this intermittent issue on 1 of the indexing servers. Our EV stores go into backup mode at 445am and then come out of this at 615am. For one of the servers, sometimes I find the indexing service has failed to restart after an hour or I find that event id 7318/41334 has not generated. For the index server failed issue, I generally find that a reboot of the server fixes it. For the event id, usually index store is stuck in backup mode so I have to runClear-IndexLocationBackupMode to manually clear it. Anyone else had a similar experience?1.8KViews0likes7Commentsspace needed to perform index upgrade
Hi All, I am in the process of upgrading 32 bit index for a customer. I would like to know if the size of the converted index (64 bit) will be same as the original 32 bit index. This is to get an idea of the amount of free space needed at the open index locations. Environment details: EV 11 Index Server Groups present Thanks & Regards, VJSolved1.3KViews0likes3CommentsHigh 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!809Views0likes2CommentsUpdating 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.Solved1.6KViews0likes8Comments