Provisioning volumes

If you need more storage after you launch an ONTAP Cloud system, you can provision new NFS and CIFS volumes from Cloud Manager.

Before you begin

If you want to use CIFS in AWS, you must have set up DNS and Active Directory.

AWS networking requirements

Steps

  1. On the Working Environments page, double-click the name of the ONTAP Cloud system on which you want to provision volumes.
  2. Create a new volume on any aggregate or on a specific aggregate:
    To... Do this...
    Create a new volume and let Cloud Manager choose the containing aggregate Click Add New Volume.
    Create a new 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.

    Volume Protection

    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.

  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 ONTAP Cloud Storage Virtual Machine (SVM). In most cases, the domain is the same as the AD domain.
  5. On the Usage Profile & Tiering page, choose a usage profile and disk type, and then click Go.
  6. When prompted, click Approve.

Result

ONTAP Cloud provisions the volume.

After you finish