Upgrading indexes to 64bit and the cachelocation
Looking for experience from the field:
I am in a relatively large environment (10mbx archiving servers) where there is extensive use of VaultCache for laptop-users.
The cache location (currently set at the default of 20GB with 10 concurrent connections) is on all these servers around 18 to 19gb.
If we upgrade to EV10, when starting to upgrade indexes, what is the best way to use this cache-location?
If I keep the settings as they are, does this mean upgrading indexes will either not happen (due to cache-location being full) or will it go really slow (due to waiting for space to become available). IT is possible to extend the cache-location location, but not with very large amounts.
Would it be best to disable VaultCache for laptop users during the time indexes are upgraded?
Would i need to add new servers, using these as indexing servers only? Will the upgrade of the indexes use the location on the new indexservers, or will it use the cache-location on the server where the 32bit index sits?
Is it possible to 'seperate' the cache used for index upgrades and VC builds?
IF you have had a similar environment, how did you do it?