I am having the above error coming up alongside “The search could not be performed due to the index not being searchable” for 4 users in a subset of 6504 archives being searched.
This is preventing me from accepting the results.
I am seeing some really odd behaviour on a journal archiving server with local Indexing.
First off, we are running 10.0.4 with both discovery and compliance accelerator. I haeva project in the pipeline to offload the indexing to an indexing...
Recently I removed the migration configuration for TSM on an old Store Partition (EV 9.0.2), and reconfigured the partition to use the EV Migrator and an EMC DataDomain CIFS share.
2 weeks ago the trial on one of the 12 partitions worked a ...
So yesterday I upgraded the RAM to 32GB - keeping the 32GB pagefile for the moment. Performance on the searches did improve, however I am still hitting 100 Usage on the odd occasion and during the scheduled Compliance Scans (19 of them) this...
RAM is 24GB - Pagefile 32GB.
8 CPU Cores.
Essentially what we are seeing is extremely poor performance on discovery and compliance searches. Often the server runs out of virtual memory and the services halt.
I have noted that on a regular...
The CIFS shares are accessable from all servers in the Storage Group.
I have seen no strange events beyond what normally occurs on this platform.
I'm not sure redirecting to an alternative location if a CIFS share is unavailable would ...