Before you deploy Activate for Compliance Search and eDiscovery, use these guidelines to select the appropriate hardware for your components.
Email Messages
|
Component |
Large |
Medium |
Small |
|---|---|---|---|
|
Source application size |
25 TB |
15 TB |
5 TB |
|
Objects per node (estimated)* |
250 million |
150 million |
50 million |
|
Number of mailboxes** |
5000 |
2000 |
400 |
|
CPU |
16 cores |
16 cores |
8 cores |
|
RAM |
64 GB |
32 GB |
16 GB |
|
Index disk space (SSD class disk recommended) |
10 TB |
6 TB |
2 TB |
*Based on an average message size of 100 KB. Messages with attachments are considered a single object. **Based on an average mailbox size of 5 GB, and an average of 50,000 messages per mailbox.
File Data
|
Content indexing file system data from backups |
Large |
Medium |
Small |
|---|---|---|---|
|
Source data size per node Based on the following assumptions:
|
160 TB |
80 TB |
40 TB |
|
Objects per node (estimated) |
30 million |
15 million |
7.5 million |
|
CPU or vCPU |
32 cores |
16 cores |
8 cores |
|
RAM |
64 GB |
32 GB |
16 GB |
|
Disk space |
12 TB |
6 TB |
3 TB |
Note
To get higher scalability for content indexing files from backups, you can turn off the generate previews option on the Search Engine node. When generate previews is off, each search node can accommodate approximately twice the number of objects per node. For example, in a large enterprise, this would be approximately 40 TB of source data (about 60 million objects), and the required disk space is 15% of source data (up to 6 TB).