I am learning that Enterprise Vault v9 isn't particularly fond of running out of storage at the index locations. I'm also discovering that "OPEN" and "CLOSED" index locations do not operate with the traditional interpretations of those basic words.
The administrator's guide states:
"If you are running out of disk space for indexes, you can create new index locations for the Indexing service to use to store its indexes. You can add more locations if needed. When you add a new location, the Indexing service may choose to use it when creating indexes for a new archive. If you want to force the Indexing service to use a particular location, use Close Location to close all the other locations, thus leaving just one location open.When you close a location, you prevent the Indexing service from creating new indexes there. This does not stop the Indexing service from adding to existing indexes, so you must take action before space runs out."
I closed every existing index location. I had more SAN storage allocated to the EV server. I created new index locations on this new storage and added them as OPEN in the indexing service. EV still wants to use the old (CLOSED) locations and ignore the new (OPEN) locations.
So what's an EV admin to do when the storage locations are down to 4% availability? I have additional storage (SAN) allocated to my EV server, but it appears there is no easy way to force EV to use these locations and never again use the locations that are out of space. Additionally, what I would REALLY like to do is to move a portion of the existing indexes over to the new LUNs, to free up some space on the existing storage. It looks like I'll have to modify SQL tables and that always worries me.