Even with all the due diligence paid during the design and implementation of Enterprise Vault, from time to time changes still need to be made when the environment has been in production for a while. One such change relates to Index locations, and what to do when they start to consume ‘too much’ disk space. In this sort of situation you will probably want to move some of those index volumes to a new location, even a network attached device is possible (though not always desirable for performance reasons).
In this post I’ll explain one of the options that can be used with Enterprise Vault to help with this.
Find your locations
One quick way to see which index volumes currently exist is to navigate to the Enterprise Vault Indexing Service in the Vault Admin Console, open the properties and then click on ‘Index Locations’. You might see something like this (though hopefully you won’t have them all on the C: like I have!)
You can decide that you want to perform these operations on one or all of the locations shown above. The first thing to do is to create some new locations.
Create a new folder
I normally create a new empty top level folder called something like EVIDX. This just makes things easier to find later.
Create a new location
In the Vault Admin Console on the properties of the indexing service you can then click on ‘Add’ and after entering the Vault Service Account password you to can select the newly created top level folder. Once selected Enterprise Vault will create 8 new subfolders underneath the top level folder and these are where the index volumes will reside.
You can then go through the first set of Index Locations and select ‘Close Location’. By doing this what happens is that the index volumes in that location will no longer be written to. Changes to the indexes on that location will take place in a new location.
This of course hasn’t MOVED any of your existing data, but it’s a super quick way to stop the index locations growing further. It works only in Enterprise Vault 10 by the way.