Network latency recommendations for NetWorker and Data Domain solutions

摘要: Recommendations for network latency tolerance and configuration for NetWorker and Data Domain environments

本文章適用於 本文章不適用於 本文無關於任何特定產品。 本文未識別所有產品版本。

症狀

  • Intermittent errors or failures during backup, cloning, or recovery
  • Latency or performance issues during backup, cloning, or recovery
  • Unpredictable disconnections between NetWorker and Data Domain during operations
  • Unmounting of Data Domain devices

原因

DD Boost devices do not differentiate between different TCP/IP network types. They require networks where packet loss is strictly 0% and latency is less than 20 ms to successfully operate.

解析度

Recommendations:

  • Ensure that NetWorker servers, Storage Nodes, and Clients are configured with recommended TCP and Kernel optimizations: NetWorker: Best practices for networking configuration
  • Use a minimum of two separate IP network connections to the Data Domain system: A management IP for administration and NetWorker server/node communications, and at least one IP for client connections.
  • If there are two Data Domains, and cloning occurs between them, at least one IP Data Domain to Data Domain replication. This will not be visible to or referenced by NetWorker.
  • Aggregated IPs and TCP endpoints on the Data Domain should be used to maximize throughput to the Data Domain, and can be set up using the ifgroup command.

Management IP
This is a dedicated 1 GbE data connection from the storage node directly to the Data Domain system. This connection provides a private, high-bandwidth data connection and avoids the latency and complexity of a shared data IP connection. 

 

Data transfer IP
Two or more Network Interface Cards (NIC) on the Data Domain system with 1 GbE or 10 GbE connections, which are aggregated together by using the Data Domain ifgroup command. This grouping provides increased data capacity and can improve resiliency. The Data Domain system provides automatic Advanced Load Balancing and Link Failover for NIC connections.

 

Replication IP
If Data Domain replication occurs, either outside of NetWorker or replicating using NetWorker Clone-Controlled Replication (CCR), a separate dedicated connection between the Data Domains is required to maximize throughput and minimize external competition for bandwidth.

NOTE: Attempting to manually load-balance data traffic to Data Domains within NetWorker is not recommended and can lead to other issues. Ensure that ifgroups are set up for NetWorker to be able to use a single name and IP when referencing Data Domain devices.

If different clients access the same Data Domains using different networks, advanced configuration may be required.

受影響的產品

Data Domain, NetWorker

產品

Data Domain
文章屬性
文章編號: 000038206
文章類型: Solution
上次修改時間: 27 3月 2026
版本:  5
向其他 Dell 使用者尋求您問題的答案
支援服務
檢查您的裝置是否在支援服務的涵蓋範圍內。