Skip to main content
Question

Using the hyperscale X as access node for CIFS backups

  • Nov 25, 2025 8:30 AM UTC
  • 4 replies
  • 205 views

Forum|alt.badge.img+4

Hello,

I’m trying to back up Netapp CIFS share with the Hyperscale as access node 

The hyperScale have  11.36 with ISO 3.2506

I cant choose the HSX as access node while browsing the content and the back up failed with 

“Failed to mount file share volume“

the HSX has cifs-utils installed and samba-client installed

AM I missing someting that is required for CIFS backup with Hyperscale X as access node?

4 replies

Bronco
Vaulter
Forum|alt.badge.img+3
  • Vaulter
  • Nov 25, 2025 8:56 AM UTC

Hello,

I’m trying to back up Netapp CIFS share with the Hyperscale as access node 

The hyperScale have  11.36 with ISO 3.2506

I cant choose the HSX as access node while browsing the content and the back up failed with 

“Failed to mount file share volume“

the HSX has cifs-utils installed and samba-client installed

AM I missing someting that is required for CIFS backup with Hyperscale X as access node?

Hello LiorRN,

HyperScale X nodes cannot be used as NAS Access Nodes because the HSX operating image does not include the Commvault NAS package required for CIFS/NFS traversal, and therefore CIFS shares cannot be mounted or enumerated on HSX

1. HyperScale X nodes cannot be used as NAS (CIFS/NFS) Access Nodes. HSX OS image does not include the NAS package, and therefore cannot perform SMB/CIFS scanning or mounting required for NetApp CIFS backups.

2. Even if "cifs-utils" and "samba-client" are installed, HSX still lacks the Commvault NAS components. The HSX ISO excludes:

==>  NAS Package
==>  NAS Helper Modules
==>  FUSE-based NAS scanning libraries
==>  Required Python modules for NAS traversal

3. Therefore HSX nodes will not selectable Access Nodes for NetApp CIFS shares. This is expected and documented Commvault behavior.

4. CIFS backups require a supported Access Node with NAS package installed.

Official supported types:

==>  Windows File System Agent (recommended)
==>  Linux Access Node with NAS Package (Non-HSX Linux only)

5. As a solution, deploy a separate Windows or Linux Access Node and assign it to the NetApp CIFS client.

 

Regards,

Siddharth Gandhi
 

 


Forum|alt.badge.img+4
  • Author
  • Apprentice
  • Nov 27, 2025 10:09 AM UTC

thanks


Forum|alt.badge.img+7
  • Explorer
  • Nov 17, 2026 1:46 PM UTC

Hi,

Thank you for the clarification regarding CIFS/NFS backups.

I would like to clarify whether the same limitation applies to NDMP backups.

Our environment is running Commvault 11.44 with a 3-node HyperScale/Grid cluster, and we need to back up NetApp ONTAP volumes using NDMP directly to the HyperScale Storage Pool.

Since NDMP uses the NDMP Remote Server functionality included with the MediaAgent and does not require CIFS/NFS mounting or file system traversal, can HyperScale/Grid nodes act as NDMP MediaAgents without deploying a separate proxy server?

Or is a dedicated Windows/Linux MediaAgent required for NDMP operations as well?

I'm specifically looking for confirmation of the officially supported architecture for NDMP, rather than CIFS/NFS network share backups.

Thanks!


Forum|alt.badge.img
  • Vaulter
  • Nov 18, 2026 5:48 PM UTC

Hi Jean-Paul,

NDMP should be considered separately from the CIFS/NFS Access Node limitation mentioned earlier.

For 11.44, the NDMP Agent: System Requirements explicitly lists Linux MediaAgents as supported for NDMP data protection operations. It also indicates that the required components are installed with the MediaAgent software, so this is different from the CIFS/NFS mount and file-system traversal scenario. 


For the proposed architecture:

NetApp ONTAP → NDMP → HSX MediaAgent → HyperScale Storage Pool

I don't see anything in the referenced NDMP requirements stating that a separate Windows or generic Linux MediaAgent is required solely because the destination is a HyperScale Storage Pool. There is no documentation restricting the use of HSX nodes as NDMP MediaAgents.

One additional check would be the OS/VaultOS version currently running on the HyperScale X nodes. I would verify that this platform level is included in the supported MediaAgent System Requirements for the 11.44 environment. 

If the HSX nodes are on an older OS/VaultOS level that is outside the supported requirements, then the supported HyperScale/VaultOS upgrade path should be considered rather than performing a generic Linux OS upgrade directly on the nodes.

References:

So based on the documented requirements, I would not apply the CIFS/NFS Access Node restriction to the NDMP workflow. The main validation I would make is that the specific HSX/VaultOS platform level is supported with 11.44.