There are some differences in setting up the CommVault Simpana NDMP iDataAgent in combination with NetApp Clustered Data OnTap (CDOT) compared to a 7-mode filer.
This post explains the configuration process to start backing up snapshots stored on a SnapVault NetApp running CDOT by using two-way NDMP.
In case you are using three-way NDMP to protect the data stored on the filer, some of the steps are not required. I will list those throughout the procedure.
If you need a better understanding about two-way NDMP vs. three-way NDMP, please refer to my blogpost called: “Lingo Explained: 2-way NDMP vs. 3-way NDMP”.
Before you start, ensure the CommVault Simpana software is running on a supported version. My environment is running CommVault Simpana 10 Service Pack 12 when I performed this integration. More information about the CommVault configuration prerequisites and – requirements can be found on CommVault BOL. The configuration process of NDMP on NetApp CDOT is outlined in a document called “Clustered Data OnTap 8.3 NDMP Configuration Express Guide“.
- Try to use controller-based protocols (such as CIFS & NFS) as much as possible. The filer is able to see the contents in these folders, which results in an increased flexibility in the restore process (compared to FC – or iSCSI LUN emulation).
- Create one NDMP subclient per volume instead of using one subclient containing all volumes. By splitting a higher level of performance can be achieved as data restores require less tapes to be mounted resulting in an increased recovery (limitation of the way NDMP works).
- NDMP backup data cannot be used in combination with Content Indexing (End User Search). If this is a business requirement, consider to use a pseudo client.
- Data archiving and stubbing is not supported on NDMP subclients. If this is a business requirement, consider to use a pseudo client.
- Before executing the steps outlined in this procedure, verify if all required DNS-entries are created.
- In case you are using 2-way NDMP, make sure the tape devices are presented to all controllers within the cluster before executing the procedure outlined below.