I just spotted that Exchange 2013 Cumulative Update 3 was released by the Exchange team at Microsoft. It’s a huge 1.5 GB in size. It’s great to see updates coming out so quickly, it means that problems are being addressed in nice, quick order.
In a previous article we discussed how to close off Index Locations in Enterprise Vault 10 in order to stop data being written to them. This will prevent the growth in disk space usage of where those volumes are. The next step might be that you really still have to free up some space, so you want to move some index volumes associated with particular archives. In this blog, I’ll explain how.
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).
I helped a colleague with this just the other day, and it’s quite interesting. The issue was that the Enterprise Vault Indexing Service on his Enterprise Vault 10 server would not start. He would get a pop-up saying that the service started, then immediately stopped. I had a quick look at the event log on the server, and spotted this: