Merge branch 'patch-41' of

flang-msft · flang-msft · commit 5948cc095c46 · 2025-02-21T12:21:06.000-08:00
https://github.com/animeshdas11/azure-docs into fxl Update-cache-how-to-premium-persistence.md-animeshdas
diff --git a/articles/azure-cache-for-redis/cache-how-to-premium-persistence.md b/articles/azure-cache-for-redis/cache-how-to-premium-persistence.md
@@ -18,6 +18,10 @@ ms.date: 04/10/2023
 >[!WARNING]
 > The _always write_ option for AOF persistence on the Enterprise and Enterprise Flash tiers is set to be retired on April 1, 2025. This option has significant performance limitations is no longer recommended. Using the _write every second_ option or using RDB persistence is recommended instead.
 >
+> [!IMPORTANT]
+>
+> Data persistence is meant to provide resilience for unexpected Redis node failures, but it is not a data backup or point in time recovery (PITR) feature. If corrupted data is written to the Redis instance this data will also be persisted. To make backups of your Redis instance, use the [export feature](managed-redis-how-to-import-export-data.md).  
+>
 
 ## Scope of availability
 

Original file line number	Diff line number	Diff line change
`@@ -18,6 +18,10 @@ ms.date: 04/10/2023`
`18`	`18`	`>[!WARNING]`
`19`	`19`	`> The _always write_ option for AOF persistence on the Enterprise and Enterprise Flash tiers is set to be retired on April 1, 2025. This option has significant performance limitations is no longer recommended. Using the _write every second_ option or using RDB persistence is recommended instead.`
`20`	`20`	`>`
	`21`	`+> [!IMPORTANT]`
	`22`	`+>`
	`23`	`+> Data persistence is meant to provide resilience for unexpected Redis node failures, but it is not a data backup or point in time recovery (PITR) feature. If corrupted data is written to the Redis instance this data will also be persisted. To make backups of your Redis instance, use the [export feature](managed-redis-how-to-import-export-data.md).`
	`24`	`+>`
`21`	`25`
`22`	`26`	`## Scope of availability`
`23`	`27`