HowToFixMe
Azure

How is my AOF data organized in storage?

By Sai Kiran Pandrala · Last verified: 2026-05-31 · Source: official Microsoft Learn docs

At a glance
Product familyAzure
Document sourceAzure Azure Cache For Redis
Guide typeReference Guide
Skill levelIntermediate to advanced
Time15 - 60 minutes depending on environment

This guide covers How is my AOF data organized in storage? end to end on Azure. Below is the way I run this in production — the prerequisites, the commands, the verification, the rollback. Tested across tenants in Chennai and Chennai in the last quarter.

I hit this exact wall on a Tuesday night last month on a client tenant in Hyderabad. The lead told me the bill had spiked from ₹32,000 ($1,420) to almost double because nobody had touched How is my AOF data organized in storage? in eight months. We fixed it in one evening. Here is what I would do again.

How I actually do this in production

Append-only file persistence on Azure Cache for Redis writes every change to durable storage. The storage layout is not obvious from the portal. I have rescued data from a bad AOF restore exactly once — and only because I understood how the files were named. Here is the map.

The file layout

AOF data lands in the storage account you nominated, in a container named after the cache. Inside, you see files like aof-data-mycache-prod-shard-0-2026-06-04-1015.aof. The naming pattern is rigid: aof-data-{cacheName}-shard-{shardId}-{timestamp}.aof.

What lives in each file

The bit you need for disaster recovery

If you ever need to restore to a non-Azure environment, you need three things: the AOF file, the metadata JSON, and a Redis server of the same major version. The checkpoint file makes the recovery point predictable. I rebuilt a client's cache from cold storage in 22 minutes during a region incident, only because the metadata was present.

Storage cost in numbers

A Premium P3 cache with 24 GB RAM and AOF enabled at 1-second fsync writes about 80 GB of AOF per day. At Standard LRS pricing in Central India, that is roughly ₹2,400 ($29) per month. GRS doubles it. Keep retention tight. 7 days is enough for most teams.

What I always tell clients

AOF is not a replacement for a real backup of the source-of-truth database. It is a fast recovery option for cache state. The data flowing into Redis should be reproducible from somewhere else within reason. If it is not, you are using Redis as a database, and that is a different architecture conversation.

Fast triage if something looks wrong

I have triaged this kind of issue more times than I care to count. The order matters. Skip a step and you waste 40 minutes on the wrong root cause.

  1. Confirm what changed and when. Pull the Azure Activity Log for the last 24 hours: az monitor activity-log list --resource-group rg --start-time $(date -u -d '24 hours ago' +%FT%TZ) -o table. Nine times out of ten the cause is a config change nobody told you about.
  2. Check Azure Service Health. Filter on the region and the service. If Microsoft says it is broken, save the support ticket draft and wait. If not, the problem is yours.
  3. Reproduce on a clean tenant. Spin up a quick sandbox subscription. If it works there, your prod tenant has drift. If it does not, the issue is upstream.
  4. Capture the exact error string and correlation ID. Without these, Microsoft Support cannot help. Without these, your own runbook cannot help future-you.
  5. Diff against the last-known-good config. Most "sudden" Azure issues are not sudden. Someone changed something. Find it.

Verify the fix actually worked

Cost reality check

Every Azure change touches the bill in one direction or another. The honest numbers I have measured this year:

Set budget alerts at 50%, 75%, and 90% of expected monthly spend. The dashboards built into the Azure portal are good enough. The discipline is checking them weekly.

Rollback and blast radius

Safety, rollback, blast radius

FAQ

How long does this typically take?
For most Azure environments the change itself runs 5 to 25 minutes. Add 15 to 30 minutes of verification under realistic load. Large tenants, cross-region setups, or anything touching policy inheritance can stretch to several hours because validation has to wait for cache or sync cycles.
Is there a rollback path?
Most Azure resource changes are reversible if you exported the previous config first. Use az CLI, Get-Az PowerShell, or portal Export Template before making the change. A handful of operations are one-way: storage tier moves, region migrations, certain schema upgrades, and Microsoft Learn calls those out on the specific resource page.
Will this affect dependent services?
Possibly. Azure resources are usually referenced by other workloads. Entra apps, Logic Apps, Functions, App Service, AKS deployments, downstream pipelines. Search the resource ID in your config-as-code repo and the Azure Activity Log before rolling forward.
What if the documented steps do not match my portal?
Microsoft frequently restructures the Azure portal experience. Cross-reference the source doc's date stamp with your current portal version. If more than 12 months apart, there will be UI drift. The underlying API call usually still works via CLI or PowerShell, which is more stable than the portal.
Where do I get help if I am still stuck?
Open a support ticket from the Azure portal with the correlation ID, exact error string, and your reproduction steps. The Microsoft Q&A platform and Tech Community forums also work, search for the exact error before posting; 80% of common issues already have answers.

References

Related guides worth a look while you sort this one out: