# Hardware Specifications for the ContentStore Mail Server (SMTP)

For the best performance, consider these recommendations when you prepare your ContentStore Mail Server (SMTP) access nodes.

Install the Exchange package and the ContentStore Mail Server (SMTP) on the same client.

These hardware guidelines are based on the number of messages that are sent or received per day on your ContentStore Mail Server (SMTP) access node.

Important

- For high availability, configure at least two access nodes.

- Use an access node for every 600,000 messages received per day.

- Index server supports upto 2 billion emails, with basic indexing. For emails more than 1 billion, you can create another Exchange client using same Index server. This will help to protect 2 billion emails using a single/ the same Index server.

## Index Server Size With Basic Indexing

Use these guidelines to select the appropriate hardware for the index server if you do not use content indexing. In this case, archiving and cleanup operations are considered.

Component | Large | Medium | Small
--- | --- | --- | ---
Source application size | 50 TB | 20 TB | 5 TB
Objects per node (estimated)* | 2 billion | 1 billion | 350 million
Number of mailboxes** | 10,000 | 4000 | 1000
CPU, vCPU, and RAM | CPU or vCPU: 16 cores RAM: 28 GB - 32 GB | CPU or vCPU: 8 cores RAM: 16 GB | CPU or vCPU: 4 cores RAM: 8 GB
Index disk space (SSD class disk recommended) | 3 TB | 1.5 TB | 500 GB

* Based on an average message size of 100 KB.

** Based on an average mailbox size of 5 GB, and an average of 50,000 messages per mailbox.

## Access Node Size Without Content Indexing

If you do not use content indexing, base the size of your access nodes on these guidelines.

Number of messages received per day on each access node* | Up to 50,000 | 50,000 to 300,000 | 300,000 to 600,000
CPU or vCPU, and RAM | CPU or vCPU: 4 cores RAM: 8 GB | CPU or vCPU: 8 cores RAM: 16 GB | CPU or vCPU: 12 cores RAM: 24 GB
ContentStore Mailbox cache disk size** | 100 GB | 500 GB | 1 TB
ContentStore Mailbox disk IOPS | Minimum: 200 IOPS | Minimum: 300 IOPS | Minimum: 600 IOPS
Streams per access node | 2 | 5 | 5

* Based on an average message size of 100 KB.

** The cache should have enough space to hold two-week's worth of messages in case the backup infrastructure becomes unavailable. Calculate this space based on the amount of email that you expect to be received on the Exchange server.

## Access Node Size with Content Indexing

If you use content indexing, base the size of your access nodes on these guidelines.

Number of messages received per day on each access node* | Up to 50,000 | 50,000 to 300,000 | 300,000 to 600,000
CPU or vCPU, and RAM | CPU or vCPU: 8 cores RAM: 16 GB | CPU or vCPU: 12 cores RAM: 24 GB | CPU or vCPU: 16 cores RAM: 32 GB
ContentStore Mailbox cache disk size** | 100 GB | 500 GB | 1 TB
ContentStore Mailbox disk IOPS | Minimum: 200 IOPS | Minimum: 300 IOPS | Minimum: 600 IOPS
Streams per access node | 2 | 5 | 5

* Based on an average message size of 100 KB.

** The cache should have enough space to hold two-week's worth of messages in case the backup infrastructure becomes unavailable. Calculate this space based on the amount of email that you expect to be received on the Exchange server.

×

Loading...