Oui, j'ai besoin d'une solution
I'm anticipating EV creating some large indexes due to a migration project of a significant number of PST files. Indexing is likely to be about 30TB. There will be several EV servers managing this migration activity
How should I plan my index volumes - I could create several 20TB index locations (one for each EV server) to cope with the migration and on-going steadystate, but is this too large.... Perhaps I would be better to create a larger number of smaller volumes (say 5TB??? or even 2TB??) and then actively manage the closing of these index locations as they become full and opening new locations.
Which would be more efficient for subsequent searches and e-discovery
many thanks