Why my redis exports are failing

Hi @ Desmond Sindatry

Thank you for reaching out, and I'm sorry to hear you're experiencing issues with your Redis exports failing.

Export allows you to export the data stored in Azure Cache for Redis to Redis compatible RDB file(s). You can use this feature to move data from one Azure Cache for Redis instance to another or to another Redis server. During the export process, a temporary file is created on the VM that hosts the Azure Cache for Redis server instance. Then, the file is uploaded to the chosen storage account. When the export operation completes with either a status of success or failure, the temporary file is deleted.

To help diagnose and resolve this, here are some common reasons why Azure Cache for Redis export operations might fail, along with steps you can take to troubleshoot:

Storage Account Firewall Settings:

• If the target storage account has a firewall enabled, it may block the export operation.
• Action: Check if the storage account has a firewall configured. If so, ensure the Azure Cache for Redis instance is allowed to access it. You can enable a managed identity for your Redis cache (Premium tier and above) to allow secure access to the storage account. Alternatively, temporarily allow access from the Redis cache's IP address or disable the firewall for testing.

Unsupported Blob Type:

• Exports in Azure Cache for Redis (Premium tier) require the storage account to support page blobs. If the storage account uses block blobs or other types (e.g., hot/cool tiers), you may encounter an error like "BlobTypeNotSupported."
• Action: Verify that the target storage account is a standard general-purpose V2 account or a premium page blob account. Ensure the export is configured to store RDB files as page blobs.

SAS Token Issues:

• If you're using a Shared Access Signature (SAS) token for the storage account, an invalid or expired token can cause the export to fail. For example, the SAS token's end time must be at least 1 hour from the current time, and the start time (if specified) must be at least 15 minutes in the past.
• Action: Generate a new SAS token with sufficient permissions (read, write, list, and add for the container) and ensure the time constraints are met. Then, retry the export operation.

Redis Tier Compatibility:

• The import/export feature is only available for Premium, Enterprise, and Enterprise Flash tiers. If you're using a Basic or Standard tier, exports are not supported.
• Action: Confirm that your Azure Cache for Redis instance is on a Premium or higher tier. If not, consider upgrading to a compatible tier.

To provide more specific guidance, could you share:

• The exact error message or Request ID from the export failure?
• The tier of your Azure Cache for Redis (e.g., Premium, Enterprise)?
• Whether the storage account is in the same region as the cache?
• Any firewall or VNet configurations on the cache or storage account?

Could you please refer these Documentations that might help you:

https://learn.microsoft.com/en-us/azure/azure-cache-for-redis/cache-how-to-import-export-data#export

https://techcommunity.microsoft.com/blog/azurepaasblog/common-scenarios-when-exportingimporting-azure-redis-cache/3601792

Please do "Upvote" if the above suggestion helps. If you have any further queries, please let us know. we are happy to help you.

Hi @ Desmond Sindatry

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution

please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.