The following are the hardware requirements for MediaAgent for Tape, Disk, Cloud, and Index Cache. For more information on system requirements, see System Requirement for MediaAgent.
Important
-
The following hardware requirements are applicable for non-deduplication MediaAgents.
-
The suggested workloads are not software limitations, rather design guidelines for sizing under specific conditions.
-
For large data sets that exceeds suggested capacity, we recommend that you group the similar data type agents for backups, such as File System agents, Database agents and so on.
-
The TB values are base-2.
-
To achieve the required IOPs, please consult your hardware vendor for the most suitable configuration for your implementation.
-
The index cache disk recommendation is for unstructured data types like files, VMs and granular messages. Structured data types like application, databases and so on need significantly less index cache. The recommendations given are per MediaAgent.
CPU/RAM, OS or Software Disk, and Index Cache Disk
Component |
Extra large |
Large |
Medium |
Small |
---|---|---|---|---|
CPU/RAM |
12 CPU cores, 64 GB RAM (or 12 vCPUs/64GB) |
8 CPU cores, 48 GB RAM (or 8 vCPUs/64 GB) |
4 CPU cores, 32 GB RAM (or 6 vCPUs/32 GB) |
4 CPU cores, 24 GB RAM (or 4 vCPUs/24 GB) |
OS or Software Disk |
400 GB usable disk, min 4 spindles 15K RPM or higher OR SSD class disk |
400 GB usable disk, min 4 spindles 15K RPM or higher OR SSD class disk |
400 GB usable disk, min 4 spindles 15K RPM |
400 GB usable disk, min 2 spindles 15K RPM |
Index Cache Disk3, 4 |
2 TB SSD Class Disk1, 2 |
1 TB SSD Class Disk |
1 TB local disk space with 400+ random IOPs |
400 GB local disk space with 200+ random IOPs |
Suggested Workloads
Component |
Extra large |
Large |
Medium |
Small |
---|---|---|---|---|
300 |
200 |
100 |
50 |
|
Front End Terabytes (FET)5 |
360 TB |
250 TB |
80 TB |
50 TB |
Footnotes
-
SSD class disk indicates internal dedicated endurance value drives.
-
Recommendation for unstructured data types like files, VMs and granular messages. Structured data types like application and databases require significantly less index cache.
-
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 Agent
-
Virtual Server Agents
-
NAS filers running NDMP backups
-
Backing up large file servers
-
SharePoint Agents
-
Ensuring maximum performance whenever it is critical
-
-
The index cache directory must be on a local drive. Network drives are not supported.
-
Front-End Terabytes (FET): Size of the data (for example, files, database, and mailboxes) on the client computer that have to be backed up.