Skip to content

Commit 1a2c340

Browse files
committed
application resilience warnings. new snf regions.
1 parent 7f11630 commit 1a2c340

File tree

2 files changed

+8
-0
lines changed

2 files changed

+8
-0
lines changed

articles/azure-netapp-files/azure-netapp-files-network-topologies.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -42,6 +42,7 @@ Azure NetApp Files volumes are designed to be contained in a special purpose sub
4242
* Australia Southeast
4343
* Brazil South
4444
* Canada Central
45+
* Central India
4546
* Central US
4647
* East Asia
4748
* East US
@@ -63,6 +64,7 @@ Azure NetApp Files volumes are designed to be contained in a special purpose sub
6364
* Southeast Asia
6465
* Sweden Central
6566
* Switzerland North
67+
* Switzerland West
6668
* UAE Central
6769
* UAE North
6870
* UK South

articles/azure-netapp-files/faq-application-resilience.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,13 +16,19 @@ This article answers frequently asked questions (FAQs) about Azure NetApp Files
1616

1717
Azure NetApp Files might undergo occasional planned maintenance (for example, platform updates, service or software upgrades). From a file protocol (NFS/SMB) perspective, the maintenance operations are non-disruptive, as long as the application can handle the IO pauses that might briefly occur during these events. The I/O pauses are typically short, ranging from a few seconds up to 30 seconds. The NFS protocol is especially robust, and client-server file operations continue normally. Some applications might require tuning to handle IO pauses for as long as 30-45 seconds. As such, ensure that you're aware of the application’s resiliency settings to cope with the storage service maintenance events. For human interactive applications leveraging the SMB protocol, the standard protocol settings are usually sufficient.
1818

19+
>[!IMPORTANT]
20+
>To ensure a resilient architecture, it is crucial to recognize that the cloud operates under a _shared responsibility_ model. This model encompasses the Azure cloud platform, its infrastructure services, the OS-layer, and application vendors. Each of these components plays a vital role in gracefully handling potential application disruptions that may arise during storage service maintenance events.
21+
1922
## Do I need to take special precautions for SMB-based applications?
2023

2124
Yes, certain SMB-based applications require SMB Transparent Failover. SMB Transparent Failover enables maintenance operations on the Azure NetApp Files service without interrupting connectivity to server applications storing and accessing data on SMB volumes. To support SMB Transparent Failover for specific applications, Azure NetApp Files now supports the [SMB Continuous Availability shares option](azure-netapp-files-create-volumes-smb.md#continuous-availability). Using SMB Continuous Availability is only supported for workloads on:
2225
* Citrix App Laying
2326
* [FSLogix user profile containers](../virtual-desktop/create-fslogix-profile-container.md)
2427
* Microsoft SQL Server (not Linux SQL Server)
2528

29+
>[!CAUTION]
30+
>Custom applications are not supported with SMB Continuous Availability and cannot be used with SMB Continuous Availability enabled volumes.
31+
2632
**Custom applications are not supported with SMB Continuous Availability.**
2733

2834
## I'm running IBM MQ on Azure NetApp Files. What precautions can I take to avoid disruptions due to storage service maintenance events despite using the NFS protocol?

0 commit comments

Comments
 (0)