TSM-Server Support for ONTAP NDMP CAB Feature

NetApp offers since Clustered ONTAP(cDOT) 8.2 the NDMP Feature CAB (Cluster Aware Backup).
Data Volume movements within a ONTAP Cluster (which may consist of currently up to 24 Storage Controllers; by "Vol Move" command) is an liked Feature for all cDOT customers, as it allows nondisruptive functions fore Endusers and Applicatioin-Server).
But next NDMP backup/restore process (for DUMPSMTape Format) after a "vol move" will not work clean any more without the CAB Feature Support:
- the defined ONTAP-Controller(of the DMA) will not find any more the volume for local NDMP backups (typical for SAN-connected Tape Libs).
The Problem now:
-Backup/Restore process will fail.
- TSM-Server redefinition of the ONTAP Source Controller must be done after looking for Controller, where the volume resides in the meanwhile.
- Next Differential backup will result in a Fullbackup.
- Any Restore of older NDMP Backup (before the "vol move" has been done) must be started again with the old Definition.
- For Remote Backups (where TSM uses his Tape Services on the Server instead of NetApp Tape Service), the above Problems are not given, but Data will go over an non-optimized data path: Data are moved from current ONTAP Controller by ISL Connection to the Controller defined in TSM, before transported to the TSM Server.