Skip to content

Commit edd83a6

Browse files
Merge pull request #291756 from adarshv98/patch-2
Update reliability-elastic-san.md
2 parents 20f30f3 + a912690 commit edd83a6

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/reliability/reliability-elastic-san.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: rogarana
66
ms.topic: reliability-article
77
ms.custom: subject-reliability, references_regions
88
ms.service: azure-elastic-san-storage
9-
ms.date: 02/13/2024
9+
ms.date: 12/10/2024
1010
---
1111

1212
# Reliability in Elastic SAN
@@ -31,13 +31,13 @@ To create an Elastic SAN with an availability zone enabled, see [Deploy an Elast
3131

3232
### Zone down experience
3333

34-
When deploying an Elastic SAN, if you select ZRS for your SAN's redundancy option, zonal failover is supported by the platform without manual intervention. An elastic SAN using ZRS is designed to self-heal and rebalance itself to take advantage of healthy zones automatically.
34+
If you connect using storage service endpoints, zonal failover is supported but might need manual intervention. A ZRS Elastic SAN using storage service endpoints won't switch to a healthy zone automatically. You might need to restart the iSCSI initiator to initiate a failover to a different, healthy zone.
3535

3636
If you deployed an LRS elastic SAN, you may need to deploy a new SAN, using snapshots exported to managed disks.
3737

3838
### Low-latency design
3939

40-
The latency differences between an elastic SAN on LRS and an elastic SAN on ZRS isn't particularly high. However, for workloads sensitive to latency spikes, consider an elastic SAN on LRS since it offers the lowest latency.
40+
Elastic SAN using ZRS are identical to Elastic SAN using LRS (they have the same scale targets), but ZRS does add more write latency. Benchmark your Elastic SAN to simulate the workload of your application and compare the latency between LRS and ZRS to see if it effects your workload.
4141

4242
### Availability zone migration
4343

@@ -62,4 +62,4 @@ Microsoft and its customers operate under the [Shared Responsibility Model](./av
6262
## Next steps
6363

6464
- [Plan for deploying an Elastic SAN](../storage/elastic-san/elastic-san-planning.md)
65-
- [Snapshot Azure Elastic SAN volumes (preview)](../storage/elastic-san/elastic-san-snapshots.md)
65+
- [Snapshot Azure Elastic SAN volumes (preview)](../storage/elastic-san/elastic-san-snapshots.md)

0 commit comments

Comments
 (0)