Loading...

Hardware Specification for Deduplication Four Partitioned Extended Mode

Deduplication Partitioned Extended mode configuration uses multiple MediaAgents (two to four, in a grid) to host multiple individual physical partitions (up to two deduplication databases (DDBs) per MediaAgent) of larger logical DDBs (up to two per grid). This configuration is typically used to increase the amount of FET or BET a single DDB can manage, or to allow extended/alternate retention of data in the primary DDB through a DASH-copy from the primary DDB to the secondary DDB, or to allow cross-site copies of data in a disaster recovery (DR) configuration.

You can use the deduplication partitioned extended mode in the following scenarios:

Expand All

MediaAgent Hosting DDBs of Four Sites

MediaAgent hosting the DDB of primary copy and secondary copy from four different sites.

Both primary and secondary copies data (usually from separate sources) access the same DDB MediaAgent. Usually as part of cross site DASH copy.

Long Term Retention

MediaAgent hosting four DDBs of primary and secondary copies with following retention settings:

  • Primary Copy - 90 day retention.
  • Secondary Copy - 1 to 5 years retention and DDB sealing is performed every year.

Four DDBs for Primary Copies per Grid

Protection of large amounts of unstructured data with incremental forever strategy.

In this scenario, MediaAgent hosts two DDBs of primary copy with 90 days retention.

Four DDBs for Secondary Copies per MediaAgent

Fan-in target for secondary copies from two or more DDB MediaAgents managing primary copies.

In this scenario, MediaAgent hosts two DDBs of secondary copies with 90 days retention.

The following table provides the hardware requirements for Extra Large and Large environments for deduplication partitioned extended mode. For Medium, Small and Extra Small environments, partitioned mode is not recommended.

Terms that is 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 MediaAgents in Partitioned DDB 4 4
Grid Backend Storage[1] [2] Up to 1600 TB Up to 1200TB
CPU/RAM per node 16 cores, 128 GB 12 cores, 64 GB
Disk Layout per 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
Deduplication Database (DDB) Disk 1 per node 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

Deduplication Database (DDB) Disk 2 per node 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 per node 20K dedicated Random IOPs[4] 15K dedicated Random IOPs[4]
Index Cache Disk per node[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 Up to 20000 per grid Up to 10000 per grid
Front End Terabytes (FET)
  • Primary Copy Only - 440 TB to 640 TB FET
  • Secondary Copy Only - 440TB to 640 TB FET
  • Mix of Primary and Secondary Copy:
    • 240 TB to 320 TB Primary FET AND
    • 240 TB to 320 TB Secondary FET
  • Primary Copy Only - 240 TB to 520 TB FET
  • Secondary Copy Only - 240 TB to 520 TB FET
  • Mix of Primary and Secondary Copy:
    • 160 TB to 240 TB Primary FET AND
    • 160 TB to 240 TB Secondary FET
Primary Copy Only (OR) Secondary Copy Only for Grid
  • 640 TB FET Files (includes OnePass for Files)
  • 380 TB FET of VM data (mix of VSA on VMs and MediaAgent)
  • 440 TB FET of VM and file data  (mix of VSA on VMs and MediaAgent)

Notes:

  • Assumes incremental forever strategy with periodic DASH fulls and staggered schedules
  • Combination of above data types not to exceed 380 TB to 440 TB FET on the primary copies
  • 520 TB FET Files (includes OnePass for Files))
  • 320 TB FET of VM data (mix of VSA on VMs and MediaAgent)
  • 360 TB FET of VM and File Data (mix of files, and VSA on VMs and MediaAgent)

Notes:

  • Assumes incremental forever strategy with periodic DASH fulls and staggered schedules
  • Combination of above data types not to exceed 240 TB to 360 TB FET on the primary copies
Mixed Primary and Secondary Copy for entire Grid Primary Copy
  • 320 TB FET Files (includes OnePass for Files)
  • 240 TB FET for VMs and files (mix of files with VSA on MediaAgent, and multiple VMs with VSA)
  • 240 TB FET for databases or applications

Secondary Copy

  • 320 to 240 TB FET originating from primary copy of another deduplication database
Primary Copy
  • 280 TB FET Files (includes OnePass for Files)
  • 200 TB FET for VMs and files (mix of files with VSA on MediaAgent, and multiple VMs with VSA)
  • 180 TB FET for databases or applications

Secondary Copy

  • 120 to 240 TB FET originating from primary copy of another deduplication database
Supported Targets
Tape Drives Not Recommended Not Recommended
Disk Storage without NetApp Deduplication Not Recommended Not Recommended
Deduplication Disk Storage Up to 1600 TB, direct attached or NAS Up to 1200 TB, direct attached or NAS
Third-Party Deduplication Appliances Not recommended Not Recommended
Cloud Storage Yes

Primary copy on Disk and secondary copy on Cloud

Yes

Primary copy on Disk and secondary copy on Cloud

Deploying MediaAgent on Cloud / Virtual Environments No No

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.