Loading...

Hardware Recommendations for the Index Server

The index server provides the following functions:

  • stores metadata
  • provides content indexing, if it is configured
  • browsing and searching archived messages

For more information, see Configurations for the Exchange Mailbox Agent Index Server.

Index Server Size Without Content 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)*

500 million

200 million

50 million

Number of mailboxes**

10,000

4000

1000

CPU, vCPU, and RAM

CPU or vCPU: 16 cores

RAM: 32 GB

CPU or vCPU: 8 cores

RAM: 16 GB

CPU or vCPU: 4 cores

RAM: 8 GB

Index disk space

3 TB

1.5 TB

500 GB

Index disk IOPS

Minimum: 800 IOPS

Recommended: 1600 IOPS

Minimum: 600 IOPS

Recommended: 800 IOPS

Minimum: 400 IOPS

Recommended: 600 IOPS

* 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.

Index Server Sizing with Content Indexing

Use these guidelines to select the appropriate hardware for your index server if you use content indexing. In this case, archiving, cleanup, and content indexing operations are considered. The entire message is content indexed.

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 and RAM

CPU or vCPU: 16 cores

RAM: 64 GB

CPU or vCPU: 16 cores

RAM: 32 GB

CPU or vCPU: 8 cores

RAM: 16 GB

Index disk space

10 TB

6 TB

2 TB

Index disk IOPS

Minimum: 2400 IOPS

Minimum: 1600 IOPS

Minimum: 800 IOPS

* 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.

User Mailbox and Journal Mailbox Access Nodes

Applies to: User Mailbox, and Journal Mailbox

The access node is the server that runs archiving and cleanup jobs for the User Mailbox and the Journal Mailbox.

Important

  • For high-availability, configure at least two access nodes.
  • Use an access node for every 10,000 mailboxes in your environment.
  • We recommend that you use extra access nodes and service accounts for the first full job.

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 mailboxes*

5000

10,000

Number of messages per day**

500,000

1 million

Online Service account

5

10

On-Premises Service Account

2 (1 per Exchange Server)

4(1 per Exchange Server)

CPU or vCPU, and RAM

CPU or vCPU: 4 cores

RAM: 8 GB

CPU or vCPU: 8 cores

RAM: 16 GB

Streams per access node

10

20

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

** Based on an average message size of 100 KB.

Access Node Size with Content Indexing

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

Number of mailboxes*

5000

10,000

Number of messages per day**

500,000

1 million

Online Service account

5

10

On-Premises Service Account

2 (1 per Exchange Server)

4(1 per Exchange Server)

CPU or vCPU, and RAM

CPU or vCPU: 8 cores

RAM: 16 GB

CPU or vCPU: 16 cores

RAM: 32 GB

Streams per access node

10

20

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

** Based on an average message size of 100 KB.

Last modified: 6/6/2018 10:11:39 PM