You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
NFS Azure file shares are supported in all the same regions that support premium file storage. See [Azure products available by region](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/?products=storage®ions=all).
31
32
32
-
## Prerequisites
33
+
## Step 1: Create an NFS Azure file share
33
34
34
-
-[Create an NFS share](storage-files-how-to-create-nfs-shares.md).
35
-
- Open port 2049 on the client you want to mount your NFS share to.
35
+
If you haven't already done so, [create an NFS Azure file share](storage-files-how-to-create-nfs-shares.md).
36
36
37
-
> [!IMPORTANT]
38
-
> NFS shares can only be accessed from trusted networks.
37
+
## Step 2: Configure network security
39
38
40
-
- Either [create a private endpoint](storage-files-networking-endpoints.md#create-a-private-endpoint) (recommended) or [restrict access to your public endpoint](storage-files-networking-endpoints.md#restrict-public-endpoint-access).
41
-
- To enable hybrid access to an NFS Azure file share, use one of the following networking solutions:
42
-
-[Configure a Point-to-Site (P2S) VPN on Linux for use with Azure Files](storage-files-configure-p2s-vpn-linux.md).
43
-
-[Configure a Site-to-Site VPN for use with Azure Files](storage-files-configure-s2s-vpn.md).
NFS shares can only be accessed from trusted networks. Currently, the only way to secure the data in your storage account is by using a virtual network and other network security settings. Any other tools used to secure data, including account key authorization, Microsoft Entra security, and access control lists (ACLs) can't be used to authorize an NFSv4.1 request.
45
40
46
-
## Disable secure transfer
41
+
> [!IMPORTANT]
42
+
> The NFSv4.1 protocol runs on port 2049. If you're connecting from an on-premises network, make sure that your client allows outgoing communication through those ports. If you've granted access to specific VNets, make sure that any network security groups associated with those VNets don't contain security rules that block incoming communication through those ports.
43
+
44
+
To use NFS Azure file shares, you must either [create a private endpoint](storage-files-networking-endpoints.md#create-a-private-endpoint) (recommended) or [restrict access to your public endpoint](storage-files-networking-endpoints.md#restrict-public-endpoint-access).
45
+
46
+
To enable hybrid access to an NFS Azure file share, use one of the following networking solutions:
47
+
48
+
-[Configure a Point-to-Site (P2S) VPN](storage-files-configure-p2s-vpn-linux.md).
49
+
-[Configure a Site-to-Site VPN](storage-files-configure-s2s-vpn.md).
Azure Files doesn't currently support encryption-in-transit with the NFS protocol and relies instead on network-level security. Therefore, you'll need to disable secure transfer on your storage account.
47
53
48
54
1. Sign in to the [Azure portal](https://portal.azure.com/) and access the storage account containing the NFS share you created.
49
55
1. Select **Configuration**.
@@ -52,24 +58,13 @@ Azure file shares can be mounted in Linux distributions using either the Server
52
58
53
59
:::image type="content" source="media/storage-files-how-to-mount-nfs-shares/disable-secure-transfer.png" alt-text="Screenshot of storage account configuration screen with secure transfer disabled." lightbox="media/storage-files-how-to-mount-nfs-shares/disable-secure-transfer.png":::
54
60
55
-
## Mount options
61
+
## Step 3: Mount an NFS Azure file share
56
62
57
-
The following mount options are recommended or required when mounting NFS Azure file shares.
63
+
You can mount the share using the Azure portal. You can also create a record in the **/etc/fstab**file to automatically mount the share every time the Linux server or VM boots.
|`vers`| 4 | Required. Specifies which version of the NFS protocol to use. Azure Files only supports NFS v4.1. |
62
-
|`minorversion`| 1 | Required. Specifies the minor version of the NFS protocol. Some Linux distros don't recognize minor versions on the `vers` parameter. So instead of `vers=4.1`, use `vers=4,minorversion=1`. |
63
-
|`sec`| sys | Required. Specifies the type of security to use when authenticating an NFS connection. Setting `sec=sys` uses the local UNIX UIDs and GIDs that use AUTH_SYS to authenticate NFS operations. |
64
-
|`rsize`| 1048576 | Recommended. Sets the maximum number of bytes to be transferred in a single NFS read operation. Specifying the maximum level of 1048576 bytes will usually result in the best performance. |
65
-
|`wsize`| 1048576 | Recommended. Sets the maximum number of bytes to be transferred in a single NFS write operation. Specifying the maximum level of 1048576 bytes will usually result in the best performance. |
66
-
|`noresvport`| n/a | Recommended. Tells the NFS client to use a non-privileged source port when communicating with an NFS server for the mount point. Using the `noresvport` mount option helps ensure that your NFS share has uninterrupted availability after a reconnection. Using this option is strongly recommended for achieving high availability. |
67
-
|`actimeo`| 30-60 | Recommended. Specifying `actimeo` sets all of `acregmin`, `acregmax`, `acdirmin`, and `acdirmax` to the same value. Using a value lower than 30 seconds can cause performance degradation because attribute caches for files and directories expire too quickly. We recommend setting `actimeo` between 30 and 60 seconds. |
65
+
### Mount an NFS share using the Azure portal
68
66
69
-
## Mount an NFS share using the Azure portal
70
-
71
-
> [!NOTE]
72
-
> You can use the `nconnect` Linux mount option to improve performance for NFS Azure file shares at scale. For more information, see [Improve NFS Azure file share performance](nfs-performance.md#nconnect).
67
+
You can use the `nconnect` Linux mount option to improve performance for NFS Azure file shares at scale. For more information, see [Improve NFS Azure file share performance](nfs-performance.md#nconnect).
73
68
74
69
1. Once the file share is created, select the share and select **Connect from Linux**.
75
70
1. Enter the mount path you'd like to use, then copy the script.
@@ -79,7 +74,7 @@ The following mount options are recommended or required when mounting NFS Azure
79
74
80
75
You have now mounted your NFS share.
81
76
82
-
## Mount an NFS share using /etc/fstab
77
+
###Mount an NFS share using /etc/fstab
83
78
84
79
If you want the NFS file share to automatically mount every time the Linux server or VM boots, create a record in the **/etc/fstab** file for your Azure file share. Replace `YourStorageAccountName` and `FileShareName` with your information.
85
80
@@ -89,7 +84,21 @@ If you want the NFS file share to automatically mount every time the Linux serve
89
84
90
85
For more information, enter the command `man fstab` from the Linux command line.
91
86
92
-
### Validate connectivity
87
+
### Mount options
88
+
89
+
The following mount options are recommended or required when mounting NFS Azure file shares.
|`vers`| 4 | Required. Specifies which version of the NFS protocol to use. Azure Files only supports NFSv4.1. |
94
+
|`minorversion`| 1 | Required. Specifies the minor version of the NFS protocol. Some Linux distros don't recognize minor versions on the `vers` parameter. So instead of `vers=4.1`, use `vers=4,minorversion=1`. |
95
+
|`sec`| sys | Required. Specifies the type of security to use when authenticating an NFS connection. Setting `sec=sys` uses the local UNIX UIDs and GIDs that use AUTH_SYS to authenticate NFS operations. |
96
+
|`rsize`| 1048576 | Recommended. Sets the maximum number of bytes to be transferred in a single NFS read operation. Specifying the maximum level of 1048576 bytes will usually result in the best performance. |
97
+
|`wsize`| 1048576 | Recommended. Sets the maximum number of bytes to be transferred in a single NFS write operation. Specifying the maximum level of 1048576 bytes will usually result in the best performance. |
98
+
|`noresvport`| n/a | Recommended. Tells the NFS client to use a non-privileged source port when communicating with an NFS server for the mount point. Using the `noresvport` mount option helps ensure that your NFS share has uninterrupted availability after a reconnection. Using this option is strongly recommended for achieving high availability. |
99
+
|`actimeo`| 30-60 | Recommended. Specifying `actimeo` sets all of `acregmin`, `acregmax`, `acdirmin`, and `acdirmax` to the same value. Using a value lower than 30 seconds can cause performance degradation because attribute caches for files and directories expire too quickly. We recommend setting `actimeo` between 30 and 60 seconds. |
100
+
101
+
## Step 4: Validate connectivity
93
102
94
103
If your mount failed, it's possible that your private endpoint wasn't set up correctly or isn't accessible. For details on confirming connectivity, see [Verify connectivity](storage-files-networking-endpoints.md#verify-connectivity).
95
104
@@ -271,7 +280,6 @@ To mount an NFS Azure file share snapshot to a Linux VM (NFS client) and restore
271
280
272
281
The files and directories from the snapshot should now be available in the `/media/nfs/restore` directory.
273
282
274
-
## Next steps
283
+
## Next step
275
284
276
-
- Learn more about Azure Files with [Planning for an Azure Files deployment](storage-files-planning.md).
277
-
- If you experience any issues, see [Troubleshoot NFS Azure file shares](/troubleshoot/azure/azure-storage/files-troubleshoot-linux-nfs?toc=/azure/storage/files/toc.json).
285
+
- If you experience any issues, see [Troubleshoot NFS Azure file shares](/troubleshoot/azure/azure-storage/files-troubleshoot-linux-nfs?toc=/azure/storage/files/toc.json).
0 commit comments