Maintained with ☕️ by
IcePanel logo

Every-write AOF persistence on Azure Cache for Redis Enterprise and Enterprise Flash will be retired on 1 April 2025

Share

Services

The Enterprise and Enterprise Flash tiers of Azure Cache for Redis currently offer a [data persistence feature](https://learn.microsoft.com/azure/azure-cache-for-redis/cache-how-to-premium-persistence?tabs=enterprise) in preview. During the preview period, we discovered that there were potential data loss events when using the AOF persistence feature. While we have a fix for this issue, it requires significant degradation to the performance of AOF persistence if used with the every-write setting. As a result, we are retiring the every-write AOF feature as it doesn’t provide performance to meet our bar for GA. The option to use AOF every second will remain and be available when the feature reaches GA. **Every-write AOF will be retired on 1 April 2025**, and all instances using the feature will automatically switch to use every-second AOF instead. To avoid performance degradation before the feature is retired, we recommend switching immediately to the every-second setting for AOF persistence, or to use RDB persistence. The persistence setting can be changed at any time using the Azure portal or CLI tools. Refer to our [documentation](https://aka.ms/AOFRetirement) for more information. If you have questions, please reach out to community experts in [Microsoft Q&A](https://aka.ms/azurefrontdoorqa). If you have a support plan and you need technical help, create a [support request](https://portal.azure.com/#blade/Microsoft%5FAzure%5FSupport/HelpAndSupportBlade/newsupportrequest). * Azure Cache for Redis * Retirements * [ Azure Cache for Redis](https://azure.microsoft.com/en-gb/products/cache/)