Loading...

Hardware Specifications for Deduplication Mode

The following are the hardware requirements for MediaAgent for Tape, Disk, Cloud, Deduplication Database and Index Cache. For more information on system requirements, see System Requirement for MediaAgent.

Important:

  • The following hardware requirements are applicable for MediaAgents with deduplication. The requirements do not apply for tape libraries or MediaAgents without deduplication or using third party deduplication applications.
  • The suggested workloads are not software limitations, rather design guidelines for sizing under specific conditions.
  • Prior to configuring the Large or the Extra-large MediaAgents on VMs, contact the Products team for confirmation.
Components Extra Large Large Medium Small Extra Small
Backend Size[1] [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, min 4 spindles 15K RPM or higher OR SSD class disk 400 GB usable disk, min 4 spindles 15K RPM 300 GB usable disk, min 2 spindles 15K RPM 200 GB usable disk, min 2 spindles 15K RPM
Deduplication Database (DDB) Disk 2 TB SSD Class Disk/PCIe IO Cards[3]

2 GB Controller Cache Memory

1.2 TB SSD Class Disk/PCIe IO Cards[3]

2 GB Controller Cache Memory

600 GB SSD Class Disk/PCIe IO Cards[3] 400 GB usable, min 4 spindles, 15K RPM or higher[4] 200 GB usable, min 2 spindles, 15K RPM or higher[4]
Suggested IOPS for DDB Disk 20K dedicated Random IOPS[5] 15K dedicated Random IOPS[5] 5K dedicated Random IOPS[5] 400+ IOPS 200+ IOPS
Index Cache Disk[8] 2 TB usable with 800+ IOPs [3] [6]

Note: SSD Class Disk/PCIe IO Cards is recommended for certain workloads[7]

For example: an extra large Exchange Mailbox Agent index server can contain 1 billion messages. See Configurations for the Exchange Mailbox Agent Index Server.

1.2 TB usable with 800+ IOPs [3]

Note: SSD Class Disk/PCIe IO Cards is recommended for certain workloads[7]

For example: a  large Exchange Mailbox Agent index server can contain 750 million messages. See Configurations for the Exchange Mailbox Agent Index Server.

500 GB usable with 400+ random IOPs

For example: a  medium Exchange Mailbox Agent index server can contain 500 million messages. See Configurations for the Exchange Mailbox Agent Index Server.

200 GB usable with 200+ random IOPS

For example: a  large Exchange Mailbox Agent index server can contain 250 million messages. See Configurations for the Exchange Mailbox Agent Index Server.

200 GB usable with 200+ random IOPS
Suggested Workloads
Parallel Data Stream Transfers 300 200 100 50 25
Laptop Clients 5000 2500 1500 500 200
Front End Terabytes (FET) 90 TB to 120 TB 50 TB to 100 TB 25 TB to 50 TB 10 TB to 25 TB 5 TB to 10 TB
Network backups
  • 120 TB FET files (includes OnePass™ for files)
  • 100 TB FET for multiple Virtual Machines (VMs) with Virtual Server Agent (VSA)
  • 90 TB FET for databases or applications

Note: Combination of above data types not to exceed 100 TB FET

  • 100 TB FET files (includes OnePass for files)
  • 80 TB FET for multiple VMs with VSA
  • 60 TB FET for databases or applications

Note: Combination of above data types not to exceed 80 TB FET

  • 50 TB FET files (includes OnePass for files)
  • 30 TB FET for multiple VMs with VSA
  • 25 TB FET for database or applications

Note: Combination of above data types not to exceed 30 TB FET

  • 25 TB FET files (includes OnePass for files)
  • 20 TB FET for multiple VMs with VSA
  • 10 TB FET for databases or applications

Note: Combination of above data types not to exceed 20 TB FET

  • 10 TB FET files (includes OnePass for files)
  • 10 TB FET for multiple VMs with VSA
  • 5 TB FET for databases or applications

Note: Combination of above data types not to exceed 10 TB FET

LAN free backups
  • 50 TB FET for VMs with VSA on MediaAgent, 50 TB FET mixed network backup including VMs with VSA
  • 50 TB FET with proxy for IntelliSnap, 50 TB FET of mixed network backups
  • 40 TB FET for VMs with VSA on MediaAgent, 40 TB FET mixed network backup including VMs with VSA
  • 40 TB FET with proxy for IntelliSnap, 40 TB FET of mixed network backups
  • 20 TB FET VMs with VSA on MediaAgent, 10 TB FET mixed network backup including VMs with VSA
  • 20 TB FET with proxy for IntelliSnap, 10 TB FET of mixed network backups
NA NA
Supported Targets
Tape Drives
Disk Storage without NetApp Deduplication Maximum supported by storage controller/HBA Maximum supported by storage controller/HBA Maximum supported by storage controller/HBA Maximum supported by storage controller/HBA Maximum supported by storage controller/HBA
NetApp Deduplication Disk Storage Up to 200 TB, direct attached (OR) NAS Up to 150 TB, direct attached (OR) NAS Up to 60 TB, direct attached (OR) NAS Up to 30 TB, direct attached (OR) NAS Up to 15 TB, direct attached (OR) NAS
Third-Party Deduplication Appliances Not supported with NetApp Deduplication Yes

Exception: Some functionality might be limited, e.g., Synthetic Fulls

Yes

Exception: Some functionality might be limited, e.g., Synthetic Fulls

Yes

Exception: Some functionality might be limited, e.g., Synthetic Fulls

Yes

Exception: Some functionality might be limited, e.g., Synthetic Fulls

Cloud Storage
Deploying MediaAgent on Cloud / Virtual Environments NA NA Yes, follow vCPU recommendations Yes, follow vCPU recommendations Yes, follow vCPU recommendations

Notes:

  • 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.
  1. Maximum size per DDB.
  2. Assumes standard retention of up to 90 days. Larger retention will affect FET managed by this configuration, the backend capacity remains the same.
  3. SSD class disk indicates PCIe based cards or internal dedicated endurance value drives.
  4. Recommend dedicated RAID 1 or RAID 10 group.
  5. When multiple DDBs are on the volume, each DDB needs dedicated IOPs. IOPs may be limited by SAN controller even though SSD drives are used.
  6. 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.
  7. For the following data-intensive use cases, placing your index data on a solid-state drive (SSD) might provide better 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

  8. Assumes retention of up to 15 days.