Skip to content

Commit 907c0cc

Browse files
authored
Added persistence info for Enterprise
Data persistence in Enterprise and Enterprise Flash tiers are in preview. This wasn't reflected in the doc as it currently stands.
1 parent c6eb7bf commit 907c0cc

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/azure-cache-for-redis/cache-high-availability.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ Various high availability options are available in the Standard, Premium, and En
2222
| [Zone redundancy](#zone-redundancy) | Multi-node replicated configuration across Availability Zones, with automatic failover | 99.9% in Premium; 99.99% in Enterprise (see [details](https://azure.microsoft.com/support/legal/sla/cache/v1_1/)) |-|||
2323
| [Geo-replication](#geo-replication) | Linked cache instances in two regions, with user-controlled failover | Premium; Enterprise (see [details](https://azure.microsoft.com/support/legal/sla/cache/v1_1/)) |-|Passive|Active|
2424
| [Import/Export](#importexport) | Point-in-time snapshot of data in cache. | 99.9% (see [details](https://azure.microsoft.com/support/legal/sla/cache/v1_1/)) |-|||
25-
| [Persistence](#persistence) | Periodic data saving to storage account. | 99.9% (see [details](https://azure.microsoft.com/support/legal/sla/cache/v1_1/)) |-||-|
25+
| [Persistence](#persistence) | Periodic data saving to storage account. | 99.9% (see [details](https://azure.microsoft.com/support/legal/sla/cache/v1_1/)) |-||Preview|
2626

2727
## Standard replication for high availability
2828

@@ -81,7 +81,7 @@ When a data node becomes unavailable or a network split happens, a failover simi
8181

8282
## Persistence
8383

84-
Applicable tiers: **Premium**
84+
Applicable tiers: **Premium**, **Enterprise (Preview)**, **Enterprise Flash (Preview)**
8585

8686
Because your cache data is stored in memory, a rare and unplanned failure of multiple nodes can cause all the data to be dropped. To avoid losing data completely, [Redis persistence](https://redis.io/topics/persistence) allows you to take periodic snapshots of in-memory data, and store it to your storage account. If you experience a failure across multiple nodes causing data loss, your cache loads the snapshot from storage account. For more information, see [Configure data persistence for a Premium Azure Cache for Redis instance](cache-how-to-premium-persistence.md).
8787

0 commit comments

Comments
 (0)