Considerations for NetApp Clustered Data ONTAP SVMs
Last updated
Last updated
Following are considerations and procedures for SVMs:
The SVM must have access to all of the aggregates for volumes that will be used as targets for VMware Agentless Backup.
When running an agentless backup to an SVM on the NetApp Clustered Data ONTAP, the aggregate must be already assigned to the SVM. The following command provides you with a list of assigned aggregates:
vserver export-policy create -vserver $VS_NAME –policyname $DPX_EXPORT_POLICY
>vserver show -vserver <vserver_name> -fields aggr-list
To assign a new aggregate, use a command similar to the following. Note the aggregates already assigned and add them to the command so you do not accidentally remove assigned aggregates:
>vserver modify -vserver <vserver_name> -aggr-list aggr4_c01n02,...
Beginning with DPX 4.4.0, the NFS transport protocol is used for Windows agent-based Block backups to NetApp Clustered Data ONTAP storage. NFS transport protocol is used by NetApp Open Systems Backup (NOSB) to support data movement.
Linux Agent-based Block Backup to NetApp Clustered Data ONTAP storage utilizes iSCSI Transport Protocol.
A LIF network interface must be configured for every SVM, for serving the iSCSI transport protocol and NFS transport protocol. Users must configure one LIF interface per SVM for each physical node. For example, a cluster that consists of 2 physical nodes requires 2 LIF interfaces per SVM. For Catalogic DPX, always configure SVM using the management LIF address of the SVM.
If your NetApp Clustered Data ONTAP storage has multiple IP addresses for NFS, you might need to force the backup to use a specific IP address by updating your Windows client registry. The procedure is described in knowledge base article .