Skip to main content
Snapdrive for Unix

Snap disconnect procedure

Contributors
PDFs

This section explains the procedure followed for snap disconnect.

The following steps depict the snap disconnect procedure:

Steps

  1. SnapDrive for UNIX obtains host file specs from snap disconnect CLI and finds out the storage system volume.

  2. After deleting host file specs and un-mapping the LUNs, SnapDrive for UNIX checks if the current volume is a clone created by SnapDrive.

  3. If the FlexClone is created by SnapDrive, then SnapDrive for UNIX checks whether:

    1. There are any mapped LUNs in the clone volume

    2. There are any new LUNs in the cloned volume

    3. There are any new Snapshot copies

If all the conditions are satisfied, SnapDrive for UNIX deletes the cloned volume. For an unrestricted FlexClone, if RBAC is configured, then SnapDrive for UNIX does not perform substep 1 and substep 2 checks.

On storage systems with Data ONTAP version earlier than 7.2, restricted FlexClone volumes does not gets deleted by SnapDrive for UNIX. Storage system commands should be used to delete them. However, Unrestricted FlexClone volumes are deleted when the appropriate RBAC capability is provided to the user.

Related information

Role-based access control in SnapDrive for UNIX