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
Copy file name to clipboardExpand all lines: articles/storage/files/files-data-protection-overview.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Learn how to protect your data in Azure Files. Understand the conce
4
4
author: khdownie
5
5
ms.service: azure-file-storage
6
6
ms.topic: overview
7
-
ms.date: 07/23/2025
7
+
ms.date: 07/25/2025
8
8
ms.author: kendownie
9
9
# Customer intent: "As a systems administrator, I want to implement data protection for Azure file shares, so that I can ensure recovery from accidental loss, protect against ransomware, and maintain business continuity."
10
10
---
@@ -25,6 +25,8 @@ Azure Files gives you many tools to protect your data, including soft delete, sh
25
25
## Applies to
26
26
| Management model | Billing model | Media tier | Redundancy | SMB | NFS |
Copy file name to clipboardExpand all lines: articles/storage/files/files-disaster-recovery.md
+8-6Lines changed: 8 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,21 +4,23 @@ description: Learn how to recover your data in Azure Files. Understand the conce
4
4
author: khdownie
5
5
ms.service: azure-file-storage
6
6
ms.topic: concept-article
7
-
ms.date: 08/05/2024
7
+
ms.date: 07/25/2024
8
8
ms.author: kendownie
9
9
# Customer intent: "As a cloud architect, I want to understand the disaster recovery and failover processes for Azure Files, so that I can implement a robust data protection strategy that ensures data availability during unplanned outages."
10
10
---
11
11
12
12
# Disaster recovery and failover for Azure Files
13
13
14
-
Microsoft strives to ensure that Azure services are always available. However, unplanned service outages might occur, and you should have a disaster recovery (DR) plan in place for handling a regional service outage. An important part of a disaster recovery plan is preparing to fail over to the secondary endpoint in the event that the primary endpoint becomes unavailable. This article describes the concepts and processes involved with disaster recovery (DR) and storage account failover.
14
+
Microsoft strives to ensure that Azure services are always available. However, unplanned service outages might occur, and you should have a disaster recovery (DR) plan in place for handling a regional service outage. An important part of a disaster recovery plan is preparing to fail over to the secondary endpoint when the primary endpoint becomes unavailable. This article describes the concepts and processes involved with disaster recovery (DR) and storage account failover.
15
15
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
19
## Applies to
20
20
| Management model | Billing model | Media tier | Redundancy | SMB | NFS |
@@ -32,7 +34,7 @@ Microsoft strives to ensure that Azure services are always available. However, u
32
34
33
35
## Customer-managed planned failover (preview)
34
36
35
-
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 non-storage related outages.
37
+
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.
36
38
37
39
During the planned failover process, the primary and secondary regions are swapped. The original primary region is demoted and becomes the new secondary region. At the same time, the original secondary region is promoted and becomes the new primary. After the failover completes, users can proceed to access data in the new primary region and administrators can validate their disaster recovery plan. The storage account must be available in both the primary and secondary regions before a planned failover can be initiated.
38
40
@@ -48,7 +50,7 @@ To understand the effect of this type of failover on your users and applications
48
50
49
51
To formulate an effective DR strategy, an organization must understand:
50
52
51
-
- How much data it can afford to lose in case of a disruption (**recovery point objective** or **RPO**)
53
+
- How much data it can afford to lose in a disruption (**recovery point objective** or **RPO**)
52
54
- How quickly it needs to be able to restore business functions and data (**recovery time objective** or **RTO**)
53
55
54
56
The cost of DR generally increases with lower or zero RPO/RTO. Companies that need to be up and running in a few seconds after a disaster and can't sustain any data loss will pay more for DR, while those with higher RPO/RTO numbers will pay less. Azure provides solutions that can work with various RPO and RTO requirements.
@@ -122,7 +124,7 @@ All data already copied to the secondary is maintained when the failover happens
122
124
123
125
The **Last Sync Time (LST)** property indicates the most recent time that data from the primary region is guaranteed to have been written to the secondary region. All data written prior to the last sync time is available on the secondary, while data written after the last sync time might not have been written to the secondary and might be lost. Use this property in the event of an outage to estimate the amount of data loss you might incur by initiating an account failover.
124
126
125
-
To ensure file shares are in a consistent state when a failover occurs, a system snapshot is created in the primary region every 15 minutes and is replicated to the secondary region. When a failover occurs to the secondary region, the share state will be based on the latest system snapshot in the secondary region. If a failure happens in the primary region, the secondary region is likely behind the primary region, as all writes to the primary won't yet have been replicated to the secondary. Due to geo-lag or other issues, the latest system snapshot in the secondary region might be older than 15 minutes.
127
+
To ensure file shares are in a consistent state when a failover occurs, a system snapshot is created in the primary region every 15 minutes and is replicated to the secondary region. When a failover occurs to the secondary region, the share state is based on the latest system snapshot in the secondary region. If a failure happens in the primary region, the secondary region is likely behind the primary region, as all writes to the primary won't yet have been replicated to the secondary. Due to geo-lag or other issues, the latest system snapshot in the secondary region might be older than 15 minutes.
126
128
127
129
All write operations written to the primary region prior to the LST have been successfully replicated to the secondary region, meaning that they're available to be read from the secondary. Any write operations written to the primary region after the last sync time might or might not have been replicated to the secondary region, meaning that they might not be available for read operations.
128
130
@@ -136,7 +138,7 @@ After the storage account is reconfigured for geo-redundancy, it's possible to i
136
138
137
139
To avoid a major data loss, check the value of the **Last Sync Time** property before failing back. Compare the last sync time to the last times that data was written to the new primary to evaluate expected data loss.
138
140
139
-
After a failback operation, you can configure the new primary region to be geo-redundant again. If the original primary was configured for LRS, you can configure it to be GRS. If the original primary was configured for ZRS, you can configure it to be GZRS. For additional options, see [Change how a storage account is replicated](../common/redundancy-migration.md).
141
+
After a failback operation, you can configure the new primary region to be geo-redundant again. If the original primary was configured for LRS, you can configure it to be GRS. If the original primary was configured for ZRS, you can configure it to be GZRS. For other options, see [Change how a storage account is replicated](../common/redundancy-migration.md).
Copy file name to clipboardExpand all lines: articles/storage/files/files-redundancy.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Understand the data redundancy options available in Azure file shar
4
4
author: khdownie
5
5
ms.service: azure-file-storage
6
6
ms.topic: concept-article
7
-
ms.date: 05/20/2025
7
+
ms.date: 07/25/2025
8
8
ms.author: kendownie
9
9
ms.custom: references_regions
10
10
# Customer intent: "As a data engineer, I want to select the appropriate data redundancy option for Azure file shares, so that I can ensure optimal availability and disaster recovery tailored to my application's needs."
@@ -26,6 +26,8 @@ When you create a storage account, you choose a redundancy setting for the stora
26
26
## Applies to
27
27
| Management model | Billing model | Media tier | Redundancy | SMB | NFS |
Copy file name to clipboardExpand all lines: articles/storage/files/nfs-large-directories.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ author: khdownie
5
5
ms.service: azure-file-storage
6
6
ms.custom: linux-related-content
7
7
ms.topic: concept-article
8
-
ms.date: 01/24/2025
8
+
ms.date: 07/25/2025
9
9
ms.author: kendownie
10
10
# Customer intent: "As a Linux administrator, I want to optimize performance when accessing large directories in Azure file shares, so that I can reduce latency and improve efficiency in file enumeration and management tasks."
11
11
---
@@ -17,6 +17,8 @@ This article provides recommendations for working with directories that contain
17
17
## Applies to
18
18
| Management model | Billing model | Media tier | Redundancy | SMB | NFS |
Copy file name to clipboardExpand all lines: articles/storage/files/understand-performance.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Learn about the factors that can impact Azure file share performanc
4
4
author: khdownie
5
5
ms.service: azure-file-storage
6
6
ms.topic: concept-article
7
-
ms.date: 05/13/2024
7
+
ms.date: 07/25/2024
8
8
ms.author: kendownie
9
9
# Customer intent: "As a cloud storage administrator, I want to understand the factors affecting Azure file share performance, so that I can optimize configurations for IOPS, throughput, and latency to meet application demands."
10
10
---
@@ -16,6 +16,8 @@ Azure Files can satisfy performance requirements for most applications and use c
16
16
## Applies to
17
17
| 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