Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. NetBackup™ NAS Administrator's Guide
  3. Section III. Using NDMP
  4. NAS appliance information for NDMP
  5. Vendor-specific information
  6. NetApp
  7. Using NetBackup with NetApp's Data ONTAP 8.2 cluster mode
NetBackup™ NAS Administrator's Guide

Using NetBackup with NetApp's Data ONTAP 8.2 cluster mode

In the Clustered Data ONTAP (cDOT) 8.2 release, NetApp released an NDMP extension called Cluster Aware Backup (CAB). This extension allows backing up a Vserver (virtual server) or storage virtual machine (SVM) as an NDMP host (client) in a NetBackup policy. It is the default in new installs of ONTAP 8.2 and beyond. In environments where a cluster is upgraded from an older version of ONTAP, or in environments running multiple ONTAP versions, the behavior is to use node names as the NDMP host name. This is configurable using the following ONTAP command:

system services ndmp node-scope-mode [on|off]

Where on is Node-scope NDMP mode, and off is Vserver Aware NDMP mode.

ONTAP 8.2 C-mode (cluster mode) allows volumes to be moved from one node to another node in a cluster. Movement of volumes is performed to provide non-disruptive operations, high availability (failover), and resource balancing. NetApp automatically moves volumes during a failover. However, moving volumes to another node for maintenance or to provide load balancing will be performed by the NetApp storage admin.

NetBackup supports the CAB extension. There are important considerations when configuring NetBackup to protect a NetApp Clustered Data ONTAP environment running in either node-scope NDMP mode or Vserver Aware NDMP mode.

In NetBackup, data is tracked by client name, which is the NDMP hostname that is used to access the data. In cDOT, data is associated with a Vserver and hosted on a physical node. These things need to be considered when configuring NetBackup.

Another consideration is the availability of resources from the cluster, as illustrated in Table: Availability of resources from the cluster:

Table: Availability of resources from the cluster

Interface Type

Volume Visibility

Tape Drive Visibility

Node-scope- mode

Vserver-mode

Node-scope- mode

Vserver-mode

Non-CAB Aware NetBackup

CAB-Aware NetBackup

Non-CAB Aware NetBackup

CAB-Aware NetBackup

Cluster Management

N/A

All volumes on the same node as LIF

All volumes in cluster

N/A

N/A

All tape drives in cluster

Intercluster

N/A

All volumes on the same node as LIF

All volumes in cluster

N/A

N/A

All tape drives in cluster

Vserver

N/A

Volumes in Vserver and hosted on same node as LIF

All volumes in Vserver

N/A

N/A

N/A

Node Name

All volumes on node

N/A

N/A

All tape drives on node

N/A

N/A

An Intercluster LIF is very similar to a Cluster Management LIF, but needs to be configured on each node of a cluster.

Feedback

Was this page helpful?
Previous

NetApp

Next

Using a node name as the NDMP client name in all versions of NetBackup

Feedback

Was this page helpful?