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
# Use Azure Monitor to Analyze Azure Files metrics
15
15
16
+
:heavy_check_mark:**Applies to:** Classic SMB and NFS file shares created with the Microsoft.Storage resource provider
17
+
18
+
:heavy_multiplication_x:**Doesn't apply to:** File shares created with the Microsoft.FileShares resource provider (preview)
19
+
16
20
Understanding how to monitor file share performance is critical to ensuring that your application is running as efficiently as possible. This article shows you how to use [Azure Monitor](/azure/azure-monitor/overview) to analyze Azure Files metrics such as availability, latency, and utilization.
17
21
18
22
See [Monitor Azure Files](storage-files-monitoring.md) for details on the monitoring data you can collect for Azure Files and how to use it.
19
23
20
-
## Applies to
21
-
| Management model | Billing model | Media tier | Redundancy | SMB | NFS |
Copy file name to clipboardExpand all lines: articles/storage/files/encryption-in-transit-for-nfs-shares.md
+6-9Lines changed: 6 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,8 +14,10 @@ ms.custom:
14
14
---
15
15
16
16
# Encryption in transit for NFS Azure file shares
17
-
18
-
This article explains how you can encrypt data in transit for NFS Azure file shares. Azure Files NFS v4.1 volumes enhance network security by enabling secure TLS connections, protecting data in transit from interception, including MITM attacks.
17
+
18
+
**Applies to:**:heavy_check_mark: NFS file shares
19
+
20
+
This article explains how you can encrypt data in transit for NFS Azure file shares. Azure Files NFSv4.1 volumes enhance network security by enabling secure TLS connections, protecting data in transit from interception, including MITM attacks.
19
21
20
22
## Overview
21
23
@@ -52,7 +54,7 @@ By enabling the **Secure transfer required** setting on the storage account, you
52
54
53
55
:::image type="content" source="./media/encryption-in-transit-nfs-shares/storage-account-settings.png" alt-text="Screenshot showing how to enable Secure transfer on a storage account." lightbox="./media/encryption-in-transit-nfs-shares/storage-account-settings.png":::
54
56
55
-
However, for users who prefer to maintain flexibility between TLS and non-TLS connections on the same storage account, the **Secure transfer** setting must remain OFF.
57
+
However, for users who prefer to maintain flexibility between TLS and non-TLS connections on the same storage account, the **Secure transfer** setting must remain off.
56
58
57
59
## Encrypt data in transit for NFS shares
58
60
@@ -225,10 +227,5 @@ If mounting issues continue, check the log files for more troubleshooting detail
:heavy_check_mark:**Applies to:** Classic SMB and NFS file shares created with the Microsoft.Storage resource provider and using the Provisioned v1 or pay-as-you-go billing model
16
+
17
+
:heavy_multiplication_x:**Doesn't apply to:** File shares created with the Microsoft.FileShares resource provider (preview) or classic file shares using the Provisioned v2 billing model
18
+
15
19
Azure always stores multiple copies of your data to protect it in the face of both planned and unplanned events. These events include transient hardware failures, network or power outages, and natural disasters. Data redundancy ensures that your storage account meets the [Service-Level Agreement (SLA) for Microsoft Online Services](https://azure.microsoft.com/support/legal/sla/storage/).
16
20
17
21
This article describes the process of changing replication settings for an existing storage account that hosts Azure file shares.
18
22
19
23
> [!IMPORTANT]
20
24
> If you're using a zonal storage account, then you must first [unpin the storage account](zonal-placement.md#unpin-a-storage-account-from-a-zone) from its zone before you can change the redundancy configuration from locally redundant storage (LRS) to a non-LRS configuration.
21
25
22
-
## Applies to
23
-
24
-
| Management model | Billing model | Media tier | Redundancy | SMB | NFS |
When deciding which redundancy configuration is best for your scenario, consider the tradeoffs between lower costs and higher availability. The factors that help determine which redundancy configuration you should choose include:
For Azure Files, data protection refers to protecting the storage account, file shares, and data within them from being deleted or modified, and for restoring data after it's been deleted or modified.
@@ -51,7 +35,7 @@ There are several reasons why you should protect your file share data.
51
35
-**Business continuity:** Prepare your infrastructure to be highly available for critical workloads.
52
36
53
37
## Back up and restore Azure file shares
54
-
You can configure [Azure Backup](../../backup/azure-file-share-backup-overview.md?toc=/azure/storage/files/toc.json) to back up your file shares using the Azure portal, Azure PowerShell, Azure CLI, or REST API. You can also [use Azure File Sync](#use-azure-file-sync-for-hybrid-cloud-backups) to back up on-premises file server data on an Azure file share.
38
+
You can configure [Azure Backup](../../backup/azure-file-share-backup-overview.md?toc=/azure/storage/files/toc.json) to back up SMB Azure file shares by using the Azure portal, Azure PowerShell, Azure CLI, or REST API. You can also [use Azure File Sync](#use-azure-file-sync-for-hybrid-cloud-backups) to back up on-premises file server data on an SMB Azure file share.
Copy file name to clipboardExpand all lines: articles/storage/files/files-disaster-recovery.md
-16Lines changed: 0 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,22 +16,6 @@ Microsoft strives to ensure that Azure services are always available. However, u
16
16
> [!IMPORTANT]
17
17
> Azure File Sync only supports storage account failover if the Storage Sync Service is also failed over. This is because Azure File Sync requires the storage account and Storage Sync Service to be in the same Azure region. If only the storage account is failed over, sync and cloud tiering operations will fail until the Storage Sync Service is failed over to the secondary region. If you want to fail over a storage account containing Azure file shares that are being used as cloud endpoints in Azure File Sync, see [Azure File Sync disaster recovery best practices](../file-sync/file-sync-disaster-recovery-best-practices.md) and [Azure File Sync server recovery](../file-sync/file-sync-server-recovery.md).
18
18
19
-
## Applies to
20
-
| Management model | Billing model | Media tier | Redundancy | SMB | NFS |
Customer-managed planned failover can also be utilized in multiple scenarios, including planned disaster recovery testing, a proactive approach to large scale disasters, or to recover from nonstorage related outages.
Copy file name to clipboardExpand all lines: articles/storage/files/files-manage-namespaces.md
+2-14Lines changed: 2 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,6 +11,8 @@ ms.author: kendownie
11
11
12
12
# How to use DFS Namespaces with Azure Files
13
13
14
+
**Applies to:**:heavy_check_mark: SMB file shares
15
+
14
16
[Distributed File Systems Namespaces](/windows-server/storage/dfs-namespaces/dfs-overview), commonly referred to as DFS Namespaces or DFS-N, is a Windows Server server role that's used to simplify the deployment and maintenance of SMB file shares in production. DFS Namespaces provides storage namespace virtualization, enabling you to provide a layer of indirection between the UNC path of your file share and the actual file share. DFS Namespaces works with SMB file shares, agnostic of where those file shares are hosted. It can be used with SMB shares hosted on an on-premises Windows File Server with or without Azure File Sync, Azure file shares directly, SMB file shares hosted in Azure NetApp Files or other third-party offerings, and even with file shares hosted in other clouds.
15
17
16
18
At its core, DFS Namespaces provides a mapping between a user-friendly UNC path, like `\\contoso\shares\ProjectX` and the underlying UNC path of the SMB share like `\\Server01-Prod\ProjectX` or `\\storageaccount.file.core.windows.net\projectx`. When the end user wants to navigate to their file share, they type in the user-friendly UNC path, but their SMB client accesses the underlying SMB path of the mapping. You can also extend this basic concept to take over an existing file server name, such as `\\MyServer\ProjectX`. You can use this capability to achieve the following scenarios:
@@ -29,20 +31,6 @@ You can see an example of how to use DFS Namespaces with your Azure Files deploy
29
31
30
32
If you already have a DFS Namespace in place, no special steps are required to use it with Azure Files and File Sync. If you're accessing your Azure file share from on-premises, normal networking considerations apply. See [Azure Files networking considerations](./storage-files-networking-overview.md) for more information.
31
33
32
-
## Applies to
33
-
| Management model | Billing model | Media tier | Redundancy | SMB | NFS |
![prmerger-automator[bot]](https://avatars.githubusercontent.com/u/22479449?v=4&size=40){kind=avatar}
0 commit comments