Creating SnapLock volumes

You can use System Manager to create a SnapLock Compliance volume or a SnapLock Enterprise volume. When you create a volume, you can also set retention times, and choose whether to automate setting the WORM state on data in the volume.

Before you begin

About this task

Steps

  1. Click Storage > Volumes.
  2. Click Create > Create FlexVol.
  3. Browse and select the storage virtual machine (SVM) in which you want to create the volume.
  4. In the Create Volume dialog box, specify a new name if you want to change the default name of the volume.
    You cannot change the name of a SnapLock Compliance volume after you create the volume.
  5. Select the container aggregate for the volume.
    You must select a SnapLock Compliance aggregate or SnapLock Enterprise aggregate to create a SnapLock volume. The volume inherits the SnapLock type from the aggregate, and the SnapLock type cannot be changed after the volume is created; therefore, you must select the correct aggregate.
  6. Select the Encrypted checkbox to enable encryption for the volume.
    This option is available only if you have enabled the Volume Encryption license and if the corresponding platform is capable of supporting encryption.
  7. Select the type of storage for which you are creating this volume.
    If you are creating a SnapMirror destination volume, you must select Data Protection. You are provided read-only access to this volume.
  8. Specify the size of the volume and the percentage of the total volume size that you want to reserve for Snapshot copies.
    The default space that is reserved for Snapshot copies is zero percent for SAN and VMware volumes. For NAS volumes, the default is 5 percent.
  9. Optional: Select Thin Provisioned to enable thin provisioning for the volume.
    When thin provisioning is enabled, space is allocated to the volume from the aggregate only when data is written to the volume.
  10. Optional: Make the required changes in the Storage Efficiency tab to enable deduplication on the volume.
    System Manager uses the default deduplication schedule. If the specified volume size exceeds the limit that is required for running deduplication, the volume is created, and deduplication is not enabled.
  11. Select the SnapLock tab, and then perform the following steps:
    1. Optional: Specify the autocommit period.
      The file in the volume will remain unchanged for the period that you specify before the file is committed to the WORM state. To set files to the WORM state manually, you must select Not specified as the autocommit setting.

      The values must be in the range of 5 minutes to 10 years.

    2. Specify the minimum retention period and maximum retention period.
      The values must be in the range of 1 day through 70 years or Infinite.
    3. Select the default retention period.
      The default retention period must be within the specified minimum retention period and maximum retention period.
  12. Optional: Select the Manage Storage Quality of Service checkbox in the Quality of Service tab to enable storage QoS for the FlexVol volume in order to manage workload performance.
  13. Create a new storage QoS policy group or select an existing policy group to control the input/output (I/O) performance of the FlexVol volume.
    If you want to... Do this...
    Create a new policy group
    1. Select New Policy Group.
    2. Specify the policy group name.
    3. Specify the minimum throughput limit.
      • You can set the minimum throughput limit only on an AFF platform.
      • You cannot set the minimum throughput limit for volumes on a FabricPool-enabled aggregate.
      • If you do not specify the minimum throughput value or if the minimum throughput value is set to 0, the system automatically displays "None" as the value.

        This value is case-sensitive.

    4. Specify the maximum throughput limit to ensure that the workload of the objects in the policy group does not exceed the specified throughput limit.
      • The minimum throughput limit and the maximum throughput limit must be of the same unit type.
      • If you do not specify the minimum throughput limit, then you can set the maximum throughput limit in IOPS, B/s, KB/s, MB/s, and so on.
      • If you do not specify the maximum throughput value, the system automatically displays "Unlimited" as the value.

        This value is case-sensitive. The unit that you specify does not affect the maximum throughput.

    Select an existing policy group
    1. Select Existing Policy Group, and then click Choose to select an existing policy group from the Select Policy Group dialog box.
    2. Specify the minimum throughput limit.
      • You can set the minimum throughput limit only on an AFF platform.
      • You cannot set the minimum throughput limit for volumes on a FabricPool-enabled aggregate.
      • If you do not specify the minimum throughput value or if the minimum throughput value is set to 0, the system automatically displays "None" as the value.

        This value is case-sensitive.

    3. Specify the maximum throughput limit to ensure that the workload of the objects in the policy group does not exceed the specified throughput limit.
      • The minimum throughput limit and the maximum throughput limit must be of the same unit type.
      • If you do not specify the minimum throughput limit, then you can set the maximum throughput limit in IOPS, B/s, KB/s, MB/s, and so on.
      • If you do not specify the maximum throughput value, the system automatically displays "Unlimited" as the value.

        This value is case-sensitive. The unit that you specify does not affect the maximum throughput.

      If the policy group is assigned to more than one object, the maximum throughput that you specify is shared among the objects.

  14. Perform the following steps in the Protection tab to protect the volume:
    1. Enable Volume Protection.
    2. Select a relationship for the volume by using the Volume Relationship Type list.
    3. Select a cluster and an SVM for the destination volume.
      If the selected cluster is running a version of ONTAP software earlier than ONTAP 9.3, then only peered SVMs are listed. If the selected cluster is running ONTAP 9.3 or later, peered SVMs and permitted SVMs are listed.
    4. Specify the volume name suffix.
  15. Click Create.
  16. Verify that the volume that you created is included in the list of volumes in the Volume window.

Result

The volume is created with UNIX-style security and UNIX 700 "read write execute" permissions for the owner.