Loading...

System and Hardware Requirements (Indexing Version 1)

Table of Contents

Index Hardware Requirements

Use of SSD Disk

Primary Tape Backup

Using Iometer to Test Index Cache Directory Performance

Index Hardware Requirements

Whenever installing or reconfiguring a MediaAgent, ensure proper index cache sizing by verifying that the volume hosting the index cache has sufficient disk space. The following table shows recommended minimum system and hardware requirements for the MediaAgent.

Components

Extra Large

Large

Medium

Small

Extra Small

Backend Size1, 2

Up to 200 TB

Up to 150 TB

Up to 60 TB

Up to 30 TB

Up to 15 TB

CPU/RAM

16 CPU cores, 128 GB RAM

12 CPU cores, 64 GB RAM

8 CPU cores, 32 GB RAM (or 12 vCPUs/48 GB)

4 CPU cores, 24 GB RAM (or 6 vCPUs/32 GB)

2 CPU cores, 16 GB RAM (or 4 vCPUs/24 GB)

OS or Software Disk

400 GB SSD class disk

400 GB usable disk; minimum four spindles of 15K RPM or higher, or SSD-class disk

400 GB usable disk; minimum of four 15K RPM spindles

400 GB usable disk, minimum of two 15K RPM spindles

400 GB usable disk, minimum of two 15K RPM spindles

Index Cache Disk3, 4

2 TB SSD class disk with 5K+ dedicated random IOPS 2

1 TB SSD class disk with 5K+ dedicated random IOPS

1 TB local disk space with 400+ random IOPS

400 GB local disk space with 200+ random IOPs

400 GB local disk space with 200+ random IOPs

Number of Objects

2 billion

1 billion

1 billion

500 million

500 million

Footnotes:

  1. Assumes standard retention of up to 90 days. Larger retention will affect back end size managed by this configuration. The front end capacity remains the same.
  2. Recommendation for unstructured data types like files, VMs and granular messages. Structured data types like application, databases and so on need significantly less index cache.
  3. The index cache directory must be on a local drive. Network drives are not supported.
  4. GlusterFS is not supported.

Use of SSD Disk

To improve the indexing performance, it is recommended that you store your index data on a solid-state drive (SSD).

The following agents and cases require the best possible indexing performance:

  • Exchange Mailbox (Classic) Agent
  • Virtual Server agents (Indexing Version 1 only)
  • NAS filers running NDMP backups
  • Backing up large file servers
  • SharePoint agents
  • Any other case requiring maximum performance

Primary Tape Backup

If your data protection environment uses tape for its primary backups, consider implementing Secondary Index Server (Indexing Version 1 only) to reduce the need for off-site tape recalls.

Last modified: 1/9/2019 8:53:34 PM