NDMP TOC failure – datamover type incorrect

ANR4950E The server is unable to retrieve NDMP file history information while building table of contents for node NASNODE01, file space /SVM_NASNODE01_VIRTUALFS. NDMP node ID is 90156245149. Table of contents creation fails.

One possible cause of this can be if the datamover was defined with the wrong scope (TYPE).  
TYPE can be NAS, NASVSERVER, or NASCLUSTER.  NAS is for node context.  VSERVER is for SVM ccontext.  CLUSTER is for the whole cluster context.

NOTE: There are other possible causes, such as corrupt inodes, or other issues; however, this one bit me and was not clearly define anywhere else.

You cannot UPDATE DATAMOVER TYPE=blah, but you can simply DELETE DATAMOVER and DEFINE DATAMOVER to fix.

DEFINE datamover NASNODE01 type=nascluster dataformat=netappdump hla= user=NDMPADMIN password=PASSWORDHERE


trace disable
trace enable spi spid toc
trace begin /tmp/server.trc

Once tracing has been enabled, I would then like for you to initiate another backup of the /SVM_SBNAS01_OU_ABOD volume. When the backup completes/fails, you can then issue the following commands to disable tracing:

trace flush
trace end
trace disable

grep NDMP dsmffdc.log

NASNODE01::> node run -node SBNAS01-01
Type ‘exit’ or ‘Ctrl-D’ to return to the CLI
NASNODE01> rdfile /etc/log/backup

NetApp vs IBM terminology

NetApp is really vague about terminology translation, but a traditional RAID is called a volume group, and a distributed RAID is called a disk pool.

IBM calls both “managed disks”, and just referrs to them as RAID/TRAID vs DRAID.

The group of these is called an aggregate in OnTap, or a managed disk group in Spectrum Virtualize.

The next layer is a volume in NetApp, or a child pool (optional) in IBM.

NetApp then lets you share a volume via NFS or CIFS, or create a LUN which is really just a well aligned file in a volume. IBM calls them virtual disks, but does not offer NFS/internally.

IBM offers SONAS (Scale Out NAS) which can take LUNs from SVC and share them out. SONAS was called V7000 Unified at one point, but now the storage is unbundled. It uses General Parallel File System (GPFS aka Multi Media File System), Cluster System Manager, and a few other tried and true technologies under the covers giving a lot of options for expansion, but also a cost.


NDMP backups into a TSM storage pool will not be deduplicated.
If you set ENABLENASDEDUPE YES, that only affects NetApp backups.
IBM doesn’t make the NDMP code, so they don’t support deduplication of anything but NetApp.
That means neither IBM’s v7000 Unified backups, nor any other NDMP device, get deduplicated.

As such, go ahead and have your NDMP backups go to a DISK pool or direct to tape.
Sending to your dedupe pool will just clog things up.