Provision storage

Contributors netapp-bcammett netapp-tonacki

You can provision additional storage for your Cloud Volumes ONTAP systems from Cloud Manager by managing volumes and aggregates.

Caution All disks and aggregates must be created and deleted directly from Cloud Manager. You should not perform these actions from another management tool. Doing so can impact system stability, hamper the ability to add disks in the future, and potentially generate redundant cloud provider fees.

Create FlexVol volumes

If you need more storage after you launch your initial Cloud Volumes ONTAP system, you can create new FlexVol volumes for NFS, CIFS, or iSCSI from Cloud Manager.

Cloud Manager provides several ways to create a new volume:

  • Specify details for a new volume and let Cloud Manager handle the underlying data aggregates for you. Learn more.

  • Create volume from a template to optimize the volume for the workload requirements for certain applications, such as databases or streaming services. Learn more.

  • Create a volume on a data aggregate of your choice. Learn more.

  • Create a volume on the second node in an HA configuration. Learn more.

Before you get started

A few notes about volume provisioning:

Create a volume

Click Create volume, specify your storage needs, and let Cloud Manager handle the disk allocation for you.

Steps
  1. On the Canvas page, double-click the name of the Cloud Volumes ONTAP system on which you want to provision a FlexVol volume.

  2. Click Add Volume > New volume.

  3. Follow the steps in the wizard to create the volume.

    1. Details, Protection, and Tags: Enter basic details about the volume and select a Snapshot policy.

      Some of the fields on this page are self-explanatory. The following list describes fields for which you might need guidance:

      Field Description

      Volume Size

      The maximum size that you can enter largely depends on whether you enable thin provisioning, which enables you to create a volume that is bigger than the physical storage currently available to it.

      Tags

      Tags that you add to a volume are associated with the Application Templates service, which can help you organize and simplify the management of your resources.

      Snapshot Policy

      A Snapshot copy policy specifies the frequency and number of automatically created NetApp Snapshot copies. A NetApp Snapshot copy is a point-in-time file system image that has no performance impact and requires minimal storage. You can choose the default policy or none. You might choose none for transient data: for example, tempdb for Microsoft SQL Server.

    2. Protocol: Choose a protocol for the volume (NFS, CIFS, or iSCSI) and then provide the required information.

      If you select CIFS and a server isn’t set up, Cloud Manager prompts you to set up CIFS connectivity after you click Next.

      The following sections describe fields for which you might need guidance. The descriptions are organized by protocol.

      NFS
      Access control

      Choose a custom export policy to make the volume available to clients.

      Export policy

      Defines the clients in the subnet that can access the volume. By default, Cloud Manager enters a value that provides access to all instances in the subnet.

      CIFS
      Permissions and users/groups

      Enables you to control the level of access to an SMB share for users and groups (also called access control lists or ACLs). You can specify local or domain Windows users or groups, or UNIX users or groups. If you specify a domain Windows user name, you must include the user’s domain using the format domain\username.

      DNS Primary and Secondary IP Address

      The IP addresses of the DNS servers that provide name resolution for the CIFS server. The listed DNS servers must contain the service location records (SRV) needed to locate the Active Directory LDAP servers and domain controllers for the domain that the CIFS server will join.

      Active Directory Domain to join

      The FQDN of the Active Directory (AD) domain that you want the CIFS server to join.

      Credentials authorized to join the domain

      The name and password of a Windows account with sufficient privileges to add computers to the specified Organizational Unit (OU) within the AD domain.

      CIFS server NetBIOS name

      A CIFS server name that is unique in the AD domain.

      Organizational Unit

      The organizational unit within the AD domain to associate with the CIFS server. The default is CN=Computers.

      DNS Domain

      The DNS domain for the Cloud Volumes ONTAP storage virtual machine (SVM). In most cases, the domain is the same as the AD domain.

      NTP Server

      Select Use Active Directory Domain to configure an NTP server using the Active Directory DNS. If you need to configure an NTP server using a different address, then you should use the API. See the Cloud Manager automation docs for details.

      iSCSI
      LUN

      iSCSI storage targets are called LUNs (logical units) and are presented to hosts as standard block devices. When you create an iSCSI volume, Cloud Manager automatically creates a LUN for you. We’ve made it simple by creating just one LUN per volume, so there’s no management involved. After you create the volume, use the IQN to connect to the LUN from your hosts.

      Initiator group

      Initiator groups (igroups) specify which hosts can access specified LUNs on the storage system

      Host initiator (IQN)

      iSCSI targets connect to the network through standard Ethernet network adapters (NICs), TCP offload engine (TOE) cards with software initiators, converged network adapters (CNAs) or dedicated host bust adapters (HBAs) and are identified by iSCSI qualified names (IQNs).

    3. Disk Type: Choose an underlying disk type for the volume based on your performance needs and cost requirements.

    4. Usage Profile & Tiering Policy: Choose whether to enable or disable storage efficiency features on the volume and then select a volume tiering policy.

      ONTAP includes several storage efficiency features that can reduce the total amount of storage that you need. NetApp storage efficiency features provide the following benefits:

      Thin provisioning

      Presents more logical storage to hosts or users than you actually have in your physical storage pool. Instead of preallocating storage space, storage space is allocated dynamically to each volume as data is written.

      Deduplication

      Improves efficiency by locating identical blocks of data and replacing them with references to a single shared block. This technique reduces storage capacity requirements by eliminating redundant blocks of data that reside in the same volume.

      Compression

      Reduces the physical capacity required to store data by compressing data within a volume on primary, secondary, and archive storage.

    5. Review: Review details about the volume and then click Add.

Result

Cloud Manager creates the volume on the Cloud Volumes ONTAP system.

Create a volume from a template

If your organization has created Cloud Volumes ONTAP volume templates so you can deploy volumes that are optimized for the workload requirements for certain applications, follow the steps in this section.

The template should make your job easier because certain volume parameters will already be defined in the template, such as disk type, size, protocol, snapshot policy, cloud provider, and more. When a parameter is already predefined, you can just skip to the next volume parameter.

Note You can only create NFS or CIFS volumes when using templates.
Steps
  1. On the Canvas page, click the name of the Cloud Volumes ONTAP system on which you want to provision a volume.

  2. Click screenshot gallery options > Add Volume From Template.

    A screenshot showing how to add a new volume from a template.

  3. In the Select Template page, select the template that you want to use to create the volume and click Next.

    A screenshot of the available application templates.

    The Define Parameters page is displayed.

    A screenshot showing a blank template that you need to fill in to create a volume.

    Note You can click the checkbox Show read-only parameters to show all the fields that have been locked by the template if you want to see the values for those parameters. By default these predefined fields are hidden and only the fields you need to complete are shown.
  4. In the Context area, the Working Environment is filled in with the name of the working environment you started with. You need to select the Storage VM where the volume will be created.

  5. Add values for all of the parameters that are not hard-coded from the template. See creating volumes for details about all the parameters you need to complete to deploy a Cloud Volumes ONTAP volume.

  6. If there are no other Actions that you need to define (for example, configuring Cloud Backup), click Run Template.

    If there are other actions, click the action in the left pane to display the parameters you need to complete.

    A screenshot showing how to select additional actions that need to be completed.

    For example, if the Enable Cloud Backup action requires that you select a backup policy, you can do that now.

  7. Click Run Template.

Result

Cloud Volumes ONTAP provisions the volume and displays a page so that you can see the progress.

A screenshot showing the progress of creating your new volume from the template.

Additionally, if any secondary action is implemented in the template, for example, enabling Cloud Backup on the volume, that action is also performed.

Create a volume on a specific aggregate

If you have a good understanding of the data aggregates on your Cloud Volumes ONTAP system, you can choose a specific aggregate for a new volume.

Steps
  1. On the Canvas page, double-click the name of the Cloud Volumes ONTAP system on which you want to provision FlexVol volumes.

  2. Select the option to create a volume on a specific aggregate:

    1. Click the menu icon, and then click Advanced > Advanced allocation.

    2. Click the menu for an aggregate.

    3. Click Create volume.

  3. Enter details for the new volume, and then click Continue.

    Some of the fields in this page are self-explanatory. The following table describes fields for which you might need guidance:

    Field Description

    Size

    The maximum size that you can enter largely depends on whether you enable thin provisioning, which enables you to create a volume that is bigger than the physical storage currently available to it.

    Access control (for NFS only)

    An export policy defines the clients in the subnet that can access the volume. By default, Cloud Manager enters a value that provides access to all instances in the subnet.

    Permissions and Users / Groups (for CIFS only)

    These fields enable you to control the level of access to a share for users and groups (also called access control lists or ACLs). You can specify local or domain Windows users or groups, or UNIX users or groups. If you specify a domain Windows user name, you must include the user’s domain using the format domain\username.

    Snapshot Policy

    A Snapshot copy policy specifies the frequency and number of automatically created NetApp Snapshot copies. A NetApp Snapshot copy is a point-in-time file system image that has no performance impact and requires minimal storage. You can choose the default policy or none. You might choose none for transient data: for example, tempdb for Microsoft SQL Server.

    Advanced options (for NFS only)

    Select an NFS version for the volume: either NFSv3 or NFSv4.

    Initiator group and IQN (for iSCSI only)

    iSCSI storage targets are called LUNs (logical units) and are presented to hosts as standard block devices.

    Initiator groups are tables of iSCSI host node names and control which initiators have access to which LUNs.

    iSCSI targets connect to the network through standard Ethernet network adapters (NICs), TCP offload engine (TOE) cards with software initiators, converged network adapters (CNAs) or dedicated host bust adapters (HBAs) and are identified by iSCSI qualified names (IQNs).

    When you create an iSCSI volume, Cloud Manager automatically creates a LUN for you. We’ve made it simple by creating just one LUN per volume, so there’s no management involved. After you create the volume, use the IQN to connect to the LUN from your hosts.

  4. If you chose the CIFS protocol and the CIFS server has not been set up, specify details for the server in the Create a CIFS Server dialog box, and then click Save and continue:

    Field Description

    DNS Primary and Secondary IP Address

    The IP addresses of the DNS servers that provide name resolution for the CIFS server.

    The listed DNS servers must contain the service location records (SRV) needed to locate the Active Directory LDAP servers and domain controllers for the domain that the CIFS server will join.

    Active Directory Domain to join

    The FQDN of the Active Directory (AD) domain that you want the CIFS server to join.

    Credentials authorized to join the domain

    The name and password of a Windows account with sufficient privileges to add computers to the specified Organizational Unit (OU) within the AD domain.

    CIFS server NetBIOS name

    A CIFS server name that is unique in the AD domain.

    Organizational Unit

    The organizational unit within the AD domain to associate with the CIFS server. The default is CN=Computers.

    DNS Domain

    The DNS domain for the Cloud Volumes ONTAP storage virtual machine (SVM). In most cases, the domain is the same as the AD domain.

    NTP Server

    Select Use Active Directory Domain to configure an NTP server using the Active Directory DNS. If you need to configure an NTP server using a different address, then you should use the API. See the Cloud Manager automation docs for details.

  5. On the Usage Profile, Disk Type, and Tiering Policy page, edit the volume tiering policy, if needed.

    For help with tiering policies, refer to Data tiering overview.

  6. Click Go.

Result

Cloud Manager creates the volume on the Cloud Volumes ONTAP system.

Create a volume on the second node in an HA configuration

By default, Cloud Manager creates volumes on the first node in an HA configuration. If you need an active-active configuration, in which both nodes serve data to clients, you must create aggregates and volumes on the second node.

Steps
  1. On the Canvas page, double-click the name of the Cloud Volumes ONTAP working environment on which you want to manage aggregates.

  2. Click the menu icon and then click Advanced > Advanced allocation.

  3. Click Add Aggregate and then create the aggregate.

  4. For Home Node, choose the second node in the HA pair.

  5. After Cloud Manager creates the aggregate, select it and then click Create volume.

  6. Enter details for the new volume, and then click Create.

Result

Cloud Manager creates the volume on the second node in the HA pair.

Tip For HA pairs deployed in multiple AWS Availability Zones, you must mount the volume to clients by using the floating IP address of the node on which the volume resides.

After you create a volume

If you provisioned a CIFS share, give users or groups permissions to the files and folders and verify that those users can access the share and create a file.

If you want to apply quotas to volumes, you must use System Manager or the CLI. Quotas enable you to restrict or track the disk space and number of files used by a user, group, or qtree.

Create an aggregate

You can create aggregates yourself or let Cloud Manager do it for you when it creates volumes. The benefit of creating aggregates yourself is that you can choose the underlying disk size, which enables you to size your aggregate for the capacity or the performance that you need.

Steps
  1. On the Canvas page, double-click the name of the Cloud Volumes ONTAP instance on which you want to manage aggregates.

  2. Click the menu icon, and then click Advanced > Advanced allocation.

  3. Click Add Aggregate and then specify details for the aggregate.

    For help with disk type and disk size, see Planning your configuration.

  4. Click Go, and then click Approve and Purchase.

Connect a LUN to a host

When you create an iSCSI volume, Cloud Manager automatically creates a LUN for you. We’ve made it simple by creating just one LUN per volume, so there’s no management involved. After you create the volume, use the IQN to connect to the LUN from your hosts.

Note the following:

  1. Cloud Manager’s automatic capacity management doesn’t apply to LUNs. When Cloud Manager creates a LUN, it disables the autogrow feature.

  2. You can create additional LUNs from System Manager or the CLI.

Steps
  1. On the Canvas page, double-click the Cloud Volumes ONTAP working environment on which you want to manage volumes.

  2. Select a volume, and then click Target iQN.

  3. Click Copy to copy the iQN name.

  4. Set up an iSCSI connection from the host to the LUN.

Use FlexCache volumes to accelerate data access

A FlexCache volume is a storage volume that caches NFS read data from an origin (or source) volume. Subsequent reads to the cached data result in faster access to that data.

You can use FlexCache volumes to speed up access to data or to offload traffic from heavily accessed volumes. FlexCache volumes help improve performance, especially when clients need to access the same data repeatedly, because the data can be served directly without having to access the origin volume. FlexCache volumes work well for system workloads that are read-intensive.

Cloud Manager does not provide management of FlexCache volumes at this time, but you can use the ONTAP CLI or ONTAP System Manager to create and manage FlexCache volumes:

Starting with the 3.7.2 release, Cloud Manager generates a FlexCache license for all new Cloud Volumes ONTAP systems. The license includes a 500 GiB usage limit.