Skip to main content
Question

Commvault 11.44 - NetApp NDMP Backup to HyperScale/Grid: Access Node Requirements

  • Nov 17, 2026 1:38 PM UTC
  • 1 reply
  • 7 views

Forum|alt.badge.img+7

Hi everyone,

We are implementing a Commvault 11.44 environment with the following configuration:

  • Commvault CommServe 11.44

  • 3-node HyperScale/Grid cluster at the primary site

  • NetApp ONTAP NAS storage

  • HyperScale Storage Pool as the backup destination

We plan to back up NetApp NAS volumes using NDMP, with the backup data stored directly in the existing HyperScale Storage Pool.

I would like to clarify the following:

  1. Can HyperScale/Grid nodes be used directly as NDMP Access Nodes for NetApp ONTAP backup and restore operations in Commvault 11.44? Is this officially supported?

  2. If HyperScale/Grid nodes cannot be used as NDMP Access Nodes, is the recommended approach to deploy a dedicated Windows Server VM with the MediaAgent and File System Agent packages installed and configure it as an NDMP Proxy Access Node?

  3. In this configuration, can the dedicated Proxy MediaAgent receive the NDMP backup streams from NetApp and forward the backup data to the existing HyperScale Storage Pool, without requiring a separate Disk Library or Deduplication Database on the proxy?

  4. Are there any specific requirements or limitations regarding Data Interface Pairs (DIPs), network connectivity, deduplication, or NDMP backup and restore performance when using this architecture?

Our preference is to use the existing HyperScale infrastructure without introducing additional servers unless required for a supported configuration.

I would appreciate confirmation of the recommended and officially supported architecture for Commvault 11.44, preferably with references to Commvault documentation.

Thanks in advance!

1 reply

Forum|alt.badge.img
  • Vaulter
  • Nov 18, 2026 2:20 PM UTC

Hi Jean-Paul,

Based on the Commvault 11.44 documentation, you should be able to use the existing HyperScale/Grid MediaAgent infrastructure for this NDMP design rather than introducing a separate Windows MediaAgent by default.

The key points would be:

1. HyperScale/Grid as the NDMP access node

The NDMP components are part of the MediaAgent installation. Therefore, if the HyperScale/Grid MediaAgent has the required network connectivity to the NetApp ONTAP SVM/NDMP interface, it can be used in the NDMP access-node path. A separate Windows MediaAgent is not required solely because the workload is NDMP. The supported NDMP requirements should still be checked against your exact ONTAP version. NDMP Agent: System Requirements

2. When would I introduce a proxy access node?

I would introduce a proxy only when the access node associated with the backup plan cannot directly communicate with the NetApp NAS, or when there is another reason to separate the source-side data path.

Commvault documents the proxy flow as:

NetApp → Proxy Access Node → Backup Plan Access Node → HyperScale/Grid Storage

The backup data is forwarded from the proxy to the backup-plan access node, which writes it to the media. [https://do...tions.html]

So I would not deploy a dedicated Windows VM solely for NDMP if the existing Grid nodes satisfy the connectivity and supported-configuration requirements.

3. Separate Disk Library/DDB on a proxy

If a proxy access node is required, its role does not require creating a separate Disk Library or DDB simply to forward the NDMP data.

The documented proxy architecture has the proxy transfer the data to the backup-plan access node, which handles the write to the configured storage. [https://do...tions.html]

This means you can continue using the existing HyperScale Storage Pool rather than creating another storage stack specifically for the proxy.

4. Pay particular attention to DIPs

This is probably the most important configuration item for the proposed Grid architecture.

Commvault specifically documents that NDMP backups on new Commvault Grid installations can experience connectivity failures when Data Interface Pairs are not configured for the backup network. This can happen because the NDMP operation retrieves the Storage Pool IP rather than the intended data-protection network IP. [https://do...place.html]

So I would verify/configure the required DIPs so that NDMP data uses the intended backup network rather than the storage-facing network. The 11.44 documentation explains how to configure the dedicated backup network using Data Interface Pairs. [https://do...pairs.html]

Suggested approach

Given your preference to avoid additional infrastructure, I would start with:

  1. Verify that your exact NetApp ONTAP release is supported for NDMP with Commvault 11.44. [https://do...ments.html]
  2. Configure the NetApp SVM/NAS client for NDMP.
  3. Use the existing HyperScale/Grid MediaAgent as the access node where supported and network-reachable.
  4. Validate NDMP connectivity between the NetApp interfaces and the Grid data-protection network.
  5. Configure the required DIPs for that path. [https://do...pairs.html], 
  6. Run both a backup and a restore test through that path.
  7. Introduce a proxy access node only if direct connectivity is not possible, or if you want the proxy capabilities such as source-side deduplication, load balancing or failover. Commvault also documents distributing NDMP operations across multiple proxy access nodes based on configured streams.

So, in short, I would not introduce a separate Windows MediaAgent, Disk Library or DDB as the starting design. First validate that the existing HyperScale/Grid access nodes can communicate correctly with the NetApp NDMP interfaces and make sure the DIPs are configured correctly. Add a proxy only if the network topology or another documented requirement makes it necessary.

References:

Regards,
Karthick