- Article
- 6 minutes to read
Azure NetApp Files supports creating volumes using NFS (NFSv3 or NFSv4.1), SMB3, or dual protocol (NFSv3 and SMB, or NFSv4.1 and SMB). A volume's capacity consumption counts against its pool's provisioned capacity.
This article shows you how to create an NFS volume. For SMB volumes, see Create an SMB volume. For dual-protocol volumes, see Create a dual-protocol volume.
Before you begin
- You must have already set up a capacity pool.
See Create a capacity pool. - A subnet must be delegated to Azure NetApp Files.
See Delegate a subnet to Azure NetApp Files.
Considerations
Deciding which NFS version to use
NFSv3 can handle a wide variety of use cases and is commonly deployed in most enterprise applications. You should validate what version (NFSv3 or NFSv4.1) your application requires and create your volume using the appropriate version. For example, if you use Apache ActiveMQ, file locking with NFSv4.1 is recommended over NFSv3.Security
Support for UNIX mode bits (read, write, and execute) is available for NFSv3 and NFSv4.1. Root-level access is required on the NFS client to mount NFS volumes.Local user/group and LDAP support for NFSv4.1
Currently, NFSv4.1 supports root access to volumes only. See Configure NFSv4.1 default domain for Azure NetApp Files.
Best practice
Ensure that you’re using the proper mount instructions for the volume. See Mount a volume for Windows or Linux VMs.
The NFS client should be in the same VNet or peered VNet as the Azure NetApp Files volume. Connecting from outside the VNet is supported; however, it will introduce additional latency and decrease overall performance.
Ensure that the NFS client is up to date and running the latest updates for the operating system.
Create an NFS volume
Click the Volumes blade from the Capacity Pools blade. Click + Add volume to create a volume.
In the Create a Volume window, click Create, and provide information for the following fields under the Basics tab:
Volume name
Specify the name for the volume that you are creating.Refer to Naming rules and restrictions for Azure resources for naming conventions on volumes. Additionally, you cannot use
defaultorbinas the volume name.Capacity pool
Specify the capacity pool where you want the volume to be created.Quota
Specify the amount of logical storage that is allocated to the volume.The Available quota field shows the amount of unused space in the chosen capacity pool that you can use towards creating a new volume. The size of the new volume must not exceed the available quota.
Large VolumeIf the quota of your volume is less than 100 TiB, select No. If the quota of your volume is greater than 100 TiB, select Yes.
Important
Large volumes are currently in preview. If this is your first time using large volumes, you must first register the feature and request an increase in regional capacity quota.
Volumes are considered large if they are between 100 TiB and 500 TiB in size. Once created, volumes less than 100 TiB in size cannot be resized to large volumes. Large volumes cannot be resized to less than 100 TiB and can only be resized up to 30% of lowest provisioned size. To understand the requirements and considerations of large volumes, refer to for using Requirements and considerations for large volumes.
Throughput (MiB/S)
If the volume is created in a manual QoS capacity pool, specify the throughput you want for the volume.If the volume is created in an auto QoS capacity pool, the value displayed in this field is (quota x service level throughput).
Virtual network
Specify the Azure virtual network (VNet) from which you want to access the volume.The Vnet you specify must have a subnet delegated to Azure NetApp Files. The Azure NetApp Files service can be accessed only from the same Vnet or from a Vnet that is in the same region as the volume through Vnet peering. You can also access the volume from your on-premises network through Express Route.
Subnet
Specify the subnet that you want to use for the volume.
The subnet you specify must be delegated to Azure NetApp Files.If you have not delegated a subnet, you can click Create new on the Create a Volume page. Then in the Create Subnet page, specify the subnet information, and select Microsoft.NetApp/volumes to delegate the subnet for Azure NetApp Files. In each Vnet, only one subnet can be delegated to Azure NetApp Files.
Network features
In supported regions, you can specify whether you want to use Basic or Standard network features for the volume. See Configure network features for a volume and Guidelines for Azure NetApp Files network planning for details.Availability zone
This option lets you deploy the new volume in the logical availability zone that you specify. Select an availability zone where Azure NetApp Files resources are present. For details, see Manage availability zone volume placement.If you want to apply an existing snapshot policy to the volume, click Show advanced section to expand it, specify whether you want to hide the snapshot path, and select a snapshot policy in the pull-down menu.
For information about creating a snapshot policy, see Manage snapshot policies.
Note
By default, the
.snapshotdirectory path is hidden from NFSv4.1 clients. Enabling the Hide snapshot path option will hide the .snapshot directory from NFSv3 clients; the directory will still be accessible.
Click Protocol, and then complete the following actions:
Select NFS as the protocol type for the volume.
Specify a unique file path for the volume. This path is used when you create mount targets. The requirements for the path are as follows:
- It must be unique within each subnet in the region.
- It must start with an alphabetical character.
- It can contain only letters, numbers, or dashes (
-). - The length must not exceed 80 characters.
Select the Version (NFSv3 or NFSv4.1) for the volume.
If you are using NFSv4.1, indicate whether you want to enable Kerberos encryption for the volume.
Additional configurations are required if you use Kerberos with NFSv4.1. Follow the instructions in Configure NFSv4.1 Kerberos encryption.
If you want to enable Active Directory LDAP users and extended groups (up to 1024 groups) to access the volume, select the LDAP option. Follow instructions in Configure AD DS LDAP with extended groups for NFS volume access to complete the required configurations.
Customize Unix Permissions as needed to specify change permissions for the mount path. The setting does not apply to the files under the mount path. The default setting is
0770. This default setting grants read, write, and execute permissions to the owner and the group, but no permissions are granted to other users.
Registration requirement and considerations apply for setting Unix Permissions. Follow instructions in Configure Unix permissions and change ownership mode.Optionally, configure export policy for the NFS volume.
Click Review + Create to review the volume details. Then click Create to create the volume.
The volume you created appears in the Volumes page.
A volume inherits subscription, resource group, location attributes from its capacity pool. To monitor the volume deployment status, you can use the Notifications tab.
Next steps
- Manage availability zone volume placement for Azure NetApp Files
- Configure NFSv4.1 default domain for Azure NetApp Files
- Configure NFSv4.1 Kerberos encryption
- Enable Active Directory Domain Services (AD DS) LDAP authentication for NFS volumes
- Configure AD DS LDAP with extended groups for NFS volume access
- Mount a volume for Windows or Linux VMs
- Configure export policy for an NFS volume
- Configure Unix permissions and change ownership mode.
- Resource limits for Azure NetApp Files
- Learn about virtual network integration for Azure services
- Configure access control lists on NFSv4.1 with Azure NetApp Files
- Application resilience FAQs for Azure NetApp Files
- Requirements and considerations for large volumes
Feedback
Submit and view feedback for
