Console
    Contact Us Start free

    Create a volume

    This page describes how to create a volume .

    Before you begin

    Review the following prerequisites before you create a volume:

    • You must have an existing storage pool connected to the network you intend to share the volumes to. For more information, see Storage pools overview .

    • The pool you intend to share volumes to must have enough available capacity to host the volumes.

    • If you intend to use Active Directory, make sure the correct Active Directory policy is attached to the storage pool.

    • If you want to encrypt your volume using a customer-managed encryption key (CMEK), make sure that the pool has a CMEK policy.

    • If you require LDAP access, make sure you enable the LDAP option on the pool.

    • If the existing pool doesn't meet your requirements, create a new pool.

    Capacity adjustments and constraints

    • The capacity of a volume can be increased or decreased in 1 GiB increments between its capacity limits.

    • Volume capacities are subject to the remaining available capacity in the hosting storage pool. If you run out of space, increase the capacity of the storage pool.

    • You need to provision pool or volume capacity to match the data you expect to write to it. The throughput limit of the volume is defined by its capacity and the service level for Standard, Premium, and Extreme service levels or by the pool capacity for the Flex service level.

    Create a volume

    Use the following instructions to create a volume using the Google Cloud console or Google Cloud CLI.

    Console

    1. Go to the NetApp Volumespage in the Google Cloud console.

      Go to NetApp Volumes

    2. Click Volumes.

    3. Click Create.

    4. In the Storage pool detailssection, complete the following steps:

      1. Click Select storage pool.

      2. Choose a storage pool to host the volume.

        The volume you create inherits the settings of the storage pool you select.

      3. Click Select.

        If the storage pools in the list don't have the settings you want, click Create new storage pool .

    5. In the Volume detailssection, complete the following steps:

      1. Enter a name for the volume in the Volume namefield. The name must be unique for each project within a location.

      2. Optional: enter a description in the Descriptionfield for the volume.

    For storage pools with Flex (File type), Standard, Premium, or Extreme service level

    Complete the following steps:

    1. Enter the share name of the volume in the Share namefield. The name must be unique for each project within a location.

      For NFS exports, the share name corresponds to the export path.

    2. Enter the capacity of the volume in the Capacityfield.

      For the Flex service level of the Filetype, the volumes can have a capacity between 1 GiB and 102,400 GiB.

      For the Standard, Premium, and Extreme service levels, the volumes in storage pools can have a capacity between 100 GiB and 102,400 GiB.

      Volumes on Premium and Extreme service levels support a large capacity option, which can have volume capacities between 15 TiB and 3 PiB.

      For more information about volume capacities, see Capacity adjustments and constraints .

    3. Optional: if the selected storage pool allows auto-tiering, complete the following steps:

      1. Click Enable auto-tieringif you want to enable auto-tiering for the volume.

      2. Specify a Cooling thresholdbetween 2 to 183 days for Premium, Extreme, or custom-performance Flex zonal pools. The default cooling threshold value is 31 days.

      3. Volumes in custom-performance Flex zonal pools offer the option to enable or disable the Hot tier bypass. For more information, see Manage auto-tiering .

    4. Click the Protocol(s)drop-down list, and select the protocol you want to use. Protocol options depend on protocol choice.

      Some protocol choices require an Active Directory. For more information, see Use cases for using Active Directory .

      Protocol types
      Protocol options
      NFSv3
      NFSv4.1
      Both (NFSv3 and NFSv4.1)
      SMB
      Dual-protocol
      Enable Kerberos: choose between Kerberos with or without signing and NFS encryption in transit in the volumes export rules.
      Security style: choose the permission model (NTFS or UNIX) for the volume. See Multi-protocol user mapping.
      Enable SMB encryption: enable SMB3 transport encryption.

      When enabled, clients that don't support SMB3 encryption can't access the share.
      Hide SMB share: disable discoverability for the share using network browsing.
      Enable access-based enumeration: access-based enumeration hides files and folders that users don't have permissions to access.
      Enable continuous availability share support for SQL Server, FSLogix : enable this option only for SQL Server and FSLogix workloads that require continuous availability (CA).

    5. Click Block volume from deletion when clients are connectedin the Configuration for selected protocol(s)for volumes used as GCVE datastores. This setting is permanent.

    6. Specify the Export Policy for NFSv3, NFSv4.1, and dual-protocol types to allow client access. Settings depend on your protocol choices. Export policy definition is only required for any protocol combination that contains NFSv3 or v4.1. You can't define export policies for SMB volumes.

      If required, you can add up to 20 additional export rules. For more information, see NFS volume access control through export rules .

      1. Click to expand Export rules.

      2. Click Add rule.

      3. In Allowed Clients, specify the IPv4 addresses of the clients the export rule applies to. Enter a comma-separated list of IP addresses or CIDRs with a maximum length of 4,096 characters.

      4. In Access, select Read & Writeor Read Only.

      5. In Root Access (no_root_squash), Select Onor Off.

        An important security mechanism of NFS is to map the root user, UID 0 , to nobody, UID 65534 . We recommend that you disable root access for all of your clients, except for a few management hosts. Create a dedicated export rule with root access enabled for the management hosts.

      6. Apply protocol-specific settings based on your protocol type:

        • NFSv3, NFSv4.1, without Kerberos, and dual-protocol: Specify if the rule is Read & Writeor Read-Only.

        • NFSv4.1 with Kerberos enabled: Specify if access is not enabled, read only, or read & writefor kerberos5 (krb5), kerberos5i (krb5i), and kerberos5p (krb5p).

        • Both(NFSv3 or NFSv4.1): Specify if the rule applies to NFSv3 only, NFSv4.1 only, or both.

      7. Click Done.

    For storage pools of the Flex service level of the Unified type

    Complete the following steps:

    1. Enter the capacity of the volume in the Capacityfield.

    2. In the Protocol(s) configurationsection, select the Operating systemfrom the drop-down list. This specifies the operating system to which the volume will be attached.

    3. In the Host groupssection, you can either select an existing host group or click Add a host groupto create a new one. This initiates the host group creation workflow.

    Optional settings

    1. Optional: define a snapshot schedule:

      1. Select Make snapshot directory visibleto enable file system access to snapshot versions by clients. For more information, see NetApp Volumes volume snapshots overview .

      2. Select Allow scheduled snapshotsto configure the volume to automatically take snapshots. You can specify the number of snapshots to keep at hourly, daily, weekly, and monthly snapshot intervals. Times are specified in UTC. If you reach the maximum number of snapshots, the oldest snapshot deletes.

      3. Review your snapshot selections.

    2. Optional: define a backup schedule:

      1. Select Allow scheduled backupsto configure automatic daily, weekly, or monthly backups.

      2. Select or create a backup policy .

      3. Select or create a backup vault .

    3. Optional: in the Labelssection, click Add labelto enter relevant labels for reporting and querying purposes.

    4. Click Create.

    The new volume is listed on the Volumespage. Volumes take up to 20 minutes to create the first volume that appears in the Creatingstate. Additional volumes generate within a few seconds to a few minutes.

    gcloud

    Create a volume

    Create a volume using the following command:

    gcloud  
netapp  
volumes  
create  
 VOLUME_NAME 
  
 \ 
  
--project = 
 PROJECT_ID 
  
 \ 
  
--location = 
 LOCATION 
  
 \ 
  
--storage-pool = 
 STORAGE_POOL 
  
 \ 
  
--capacity = 
 CAPACITY 
  
 \ 
  
--protocols = 
 PROTOCOLS 
  
 \ 
  
--share-name = 
 SHARE_NAME

    Replace the following information:

    • VOLUME_NAME : the name of the volume. This name must be unique per location.

    • PROJECT_ID : the name of the project to create the volume in.

    • LOCATION : the location for the volume.

    • STORAGE_POOL : the storage pool to create the volume in.

    • CAPACITY : the capacity of the volume. It defines the capacity that NAS clients see.

    • PROTOCOLS : the NAS protocols the volume is exported with. Flex tier volumes cannot be created with dual-protocol (NFS and SMB).

      Valid choices:

      • smb
      • nfsv3
      • nfsv4
      • nfsv3,nfsv4
      • nfsv3,smb
      • nfsv4,smb

      Depending on the protocol type you choose, we recommend that you add the protocol specific parameters like export-policy or smb-settings .

    • SHARE_NAME : the NFS export path or SMB share name of the volume.

    Create an iSCSI volume

    Create an iSCSI volume in the Flex service level of the Unifiedtype pool:

    gcloud  
beta  
netapp  
volumes  
create  
 VOLUME_NAME 
  
 \ 
  
--project = 
 PROJECT_ID 
  
 \ 
  
--location = 
 LOCATION 
  
 \ 
  
--storage-pool = 
 STORAGE_POOL 
  
 \ 
  
--capacity = 
 CAPACITY 
  
 \ 
  
--protocols = 
ISCSI  
 \ 
  
--block-devices = 
 name 
 = 
 LUN_NAME 
,host-groups = 
 HOST_GROUP_NAME 
,os-type = 
 OS_TYPE 
  
 \ 
  
--snapshot-directory = 
 false

    Replace the following information:

    • VOLUME_NAME : the name of the volume. This name must be unique per location.

    • PROJECT_ID : the name of the project to create the volume in.

    • LOCATION : the location for the volume.

    • STORAGE_POOL : the storage pool to create the volume in.

    • CAPACITY : the capacity of the volume. It defines the capacity that iSCSI clients see.

    • LUN_NAME : Optional: if a name is provided, the LUN will be assigned that name. Otherwise, the LUN will be named as lun_<VOLUME_NAME> .

    • HOST_GROUP_NAME : the name of the host group to which the volume needs to be attached. Multiple host groups can be specified with a # sign separating each host group.

    • OS_TYPE : the operating system of the hosts. The supported values include LINUX , WINDOWS , and ESXI .

    For more information about additional optional flags like enabling large capacity volumes and auto-tiering, see Google Cloud SDK documentation on volume creation .

    What's next

    Manage volumes .
    Create a Mobile Website
    View Site in Mobile | Classic
    Share by: