Loading...

Hardware Specifications for Deduplication Four Partitioned Mode

Deduplication Partitioned mode configuration uses multiple MediaAgents (two to four, in a grid) to host individual physical partitions of a larger logical Deduplication Database (DDB), one DDB per MediaAgent. This configuration is typically used to increase the amount of FET or BET a single DDB can manage.

The following table provides the hardware requirements for MediaAgent hosting four partitions of the DDB in large and extra-large environments. For medium, small and extra small environments, partitioned mode is not recommended except when there is a requirement for resiliency (partition failover - when one of the partition is temporarily unavailable).

Terms that are used in the following Hardware Requirements:

  • Deduplication Node - MediaAgent hosting the DDB.
  • Grid - The collection of the deduplication nodes.

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
Number of Nodes in Grid 4 4
Grid Backend Storage[1],[2] Up to 800 TB Up to 600 TB
CPU/RAM per Deduplication Node 16 cores, 128 GB 12 cores, 64 GB
Disk Layout per Deduplication node
OS or Software Disk 400 GB SSD class disk 400 GB usable disk, min 4 spindles 15K RPM or higher OR SSD class disk
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

Suggested IOPS for each DDB Disk 20K dedicated Random IOPS[4] 15K dedicated Random IOPS[4]
Index Cache Disk[7] 2 TB usable with 800+ IOPs [3] [5]

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

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[6]

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

Suggested Workloads for Grid
Parallel Data Stream Transfers 400 300
Laptop Clients for Grid Up to 20000 per Grid Up to 10000 per Grid
Front End Terabytes (FET) Range per Grid 240 TB to 400 TB 200 TB to 320 TB
Network Backups for Grid
  • 400 TB FET Files (includes OnePass for Files)
  • 320 TB FET for multiple Virtual Machines (VMs) with Virtual Server Agent (VSA)
  • 240 TB FET for databases or applications

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

  • 320 TB FET Files (includes OnePass for Files)
  • 240 TB FET for multiple VMs with VSA
  • 160 TB for databases or applications

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

LAN-Free Backups for Grid
  • 160 TB FET VMs with one VSA on each deduplication node
  • 160 TB FET mixed network backup including VMs with VSA
  • 160 TB FET with one Proxy for IntelliSnap on each deduplication node
  • 160 TB FET of mixed network backups
  • 160 TB FET for VMs with one VSA on each deduplication node
  • 80 TB FET for mixed network backup including VMs with VSA
  • 160 TB FET with one Proxy for IntelliSnap on each deduplication node
  • 80 TB FET for mixed network backups
Supported Targets
Tape Drives
Disk Storage without NetApp Deduplication Not Recommended Not Recommended
Deduplication Disk Storage Up to 800 TB

Direct Attached (OR) NAS

Up to 600 TB

Direct Attached (OR) NAS

Third-Party Deduplication Appliances Not recommended Not Recommended
Cloud Storage
Deploying MediaAgent on Cloud / Virtual Environments NA NA

Note: The TB values are base-2.

  1. Maximum size per DDB.
  2. Assumes standard retention of up to 90 days. Larger retention might affect FET managed by the specified configuration, the backend capacity remains the same.
  3. SSD class disk indicates PCIe based cards or internal dedicated endurance value drives.
  4. When multiple DDBs are on the volume, each DDB needs dedicated IOPs. IOPs might be limited by SAN controller even though SSD drives are used.
  5. Recommendation for unstructured data types like files, VMs and granular messages. Structured data types like application, databases and so on need considerably less index cache.
  6. 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
  7. Assumes retention of up to 15 days.