Skip to main content
Snap Creator Framework

Parameters to set up cloning operations

Contributors netapp-aherbin NetAppZacharyWambold
PDFs

Several parameters are required to set up Snap Creator Server cloning operations.

Parameter Setting Description

NTAP_VOL_CLONE_RESERVE

none

file

volume

This is the space guarantee for a cloned volume.

NTAP_LUN_CLONE_RESERVATION

true

false

If set to true, space is reserved for the cloned LUNs if the cloneLun action is selected. Otherwise, space is not reserved.

NTAP_CLONE_IGROUP_MAP

Specifies the storage system, source volume, and an IGROUP. The IGROUP is then mapped to cloned LUNs that reside in the source volume or cloned LUNs that reside in the volume clone (for example, controller1:src_volume1/igroup1,src_volume2/igroup1,src_volume3/igroup1;controller2:src_volume1/igroup2,src_volume2/igroup2,src_volume3/igroup2). Note:

  • LUN clones assume the same name as their parent volume or LUN and end with _CLONE; that is, if the volume is called myvol, the clone would be myvol_CLONE.

  • Volume clones start with cl_ and end with -YYYYMMDDHHMMSS.

NTAP_CLONE_FOR_BACKUP

(Y

N)

If enabled, clones (volume and LUN) are created and then deleted after the other operations are complete. Otherwise, clones are deleted before the operations are complete. Note: If you are backing up clones to tape, this should be set to Y. If you are doing database refreshes, then you should set it to N.

NTAP_CLONE_SECONDARY

(Y

N)

If enabled, clones are created on the SnapMirror destination after the SnapMirror update is complete. Note: This setting should be used with NTAP_SNAPMIRROR_USE_SNAPSHOT, NTAP_SNAPMIRROR_WAIT, and NTAP_CLONE_SECONDARY_VOLUMES, and the cloneVol action.

NTAP_CLONE_SECONDARY_VOLUMES

This is a mapping of primary or secondary storage systems and the secondary volumes. This is required so that Snap Creator can find the secondary volumes (for example, controller1:controller1-sec/vol1;controller1:controller1-sec/vol2).

NTAP_NUM_VOL_CLONES

This is the number of volume clones you want to retain. This works similarly to the Snapshot copy retention policy. Note: This only works for volume clones that require a FlexClone license on the storage controller.

NTAP_NFS_EXPORT_HOST

Host IP

The host name or IP address where the clone should be exported. This is the host where you mount the clone volume by using NFS.

NTAP_NFS_EXPORT_ACCESS

root

read-write

read-only

The host specified in NTAP_NFS_EXPORT_HOST receives access or permission to the clone volume.

  • root

    Root access is granted.

  • read-only

    Read-only access is granted.

  • read-write

    Read/Write access is granted.

NTAP_NFS_EXPORT_PERSISTENT

true

false

Determines whether NFS export is persistent. If true is selected, the clone volume is exported and the /etc/exports file on the storage controller is updated.

NTAP_CIFS_EXPORT_ENABLE

(Y

N)

Setting to share a cloned volume using CIFS.