Views:

Summary

The required steps for creating volumes on a NetApp Clustered Data ONTAP volume are outlined for creating a volume from the command-line and from the OnCommand GUI.

 

Resolution

Disclaimer

This procedure is for ongoing administration and does not include one-time NetApp procedures that need to be performed in order to get the NetApp Clustered Data ONTAP storage system functioning with DPX for NOSB backups. This document only describes how to create NetApp volumes once the Clustered Data ONTAP storage system has been properly deployed for NOSB backups with DPX as outlined in the Deployment Guide.

Command-Line Procedure

From a cluster administration shell (not the SVM), issue the following commands, with user-defined variables in a traditional UNIX-style with a prepending dollar sign($):

vserver export-policy create -vserver $VS_NAME -policyname $DPX_EXPORT_POLICY

vserver export-policy rule create -vserver $VS_NAME -policyname $DPX_EXPORT_POLICY -ruleindex 1 -protocol any -clientmatch 0.0.0.0/0 -rorule any -rwrule any -anon 65534 -superuser any

volume create -vserver $VS_NAME -volume $VOL_NAME -policy $DPX_EXPORT_POLICY -security-style <unix|mixed> -junction-path "/$VOL_NAME" -unix-permissions 0777 [other volume properties]

Note that the junction-path name must match the volume name.

Verify the server configuration through the following commands:

export-policy rule show -vserver $VS_NAME -policyname $DPX_EXPORT_POLICY -fields vserver,policyname,ruleindex,protocol,clientmatch,rwrule,anon,superuser,allow-suid,allow-dev

volume show -vserver $VS_NAME -volume $VOL_NAME -fields unix-permissions, policy, junction-path

nfs server show -vserver $VS_NAME

 

OnCommand GUI Procedure

The following screenshots show how to configure the volume within the OnCommand GUI.

  1. Define the export policy.
  4. Ensure the volume namespace is defined where a junction point is mounted to the root of the volume with the volume name using this export policy. Note that the junction-path name must match the volume name.
  6. Define the volume with the following permission set. Mixed or UNIX security style can be used.

Notes

The backup job log clearly indicates that the NOSB technology is being used by stating “CDOT Transfer Type is [NFS]”. See the following example:

If the volume is not created properly, an error message similar to the following displays:

Message: Task 10 NDMP_LOG: id(1,744), type(NDMP_LOG_ERROR), text(Backup Err: [Failed to create file [/vol/c_ewh_Prod3/[cEHPROD3]EH-PROD3@{2249A237}/BEXIMAGE.RAW] due to file/access permission.