Create a volume

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 Volume namefield, enter a name for the volume. The name must be unique for each project within a location.

5. Optional: Enter a description in the Descriptionfield for the volume.

6. Select a storage poolto host the volume.

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

   If the storage pools in the drop-down menu don't have the settings you want, create a new storage pool .

7. In the Share namefield, enter the share name of the volume. The name must be unique for each project within a location.

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

8. In the Capacityfield, enter the capacity of the volume.

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

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

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

   The capacity of a volume can increase or decrease 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.

9. 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.

   check

   Security style: choose the permission model (NTFS or UNIX) for the volume. See Multi-protocol user mapping.

   check

   Enable SMB encryption: enable SMB3 transport encryption.
   
   When enabled, clients that don't support SMB3 encryption can't access the share.

   check

   check

   Hide SMB share: disable discoverability for the share using network browsing.

   check

   check

   Enable access-based enumeration: access-based enumeration hides files and folders that users don't have permissions to access.

   check

   check

   Enable continuous availability share support for SQL Server, FSLogix : enable this option only for SQL Server and FSLogix workloads that require continuous availability (CA).

   check

10. 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.

11. Optional: if the selected storage pool allows auto-tiering:

    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 .

12. 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 65535 . 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.

13. 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.

14. Optional: define a backup schedule:

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

    2. Select or create a backup policy .

    3. Select or create a backup vault .

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

16. 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 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.

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