encountering a critical issue while attempting to import an RDB file into our Azure Redis Cache instance (XXXXX-staging-redis).

Question

Hello Microsoft Support Team,

We are encountering a critical issue while attempting to import an RDB file into our Azure Redis Cache instance (XXXXX-staging-redis). The request fails with a generic error message:

 Error: The request to import data into cache 'XXXXX-staging-redis' failed with status 'error' and no detailed error description provided.

Context:

• The RDB file was exported from Google Cloud Platform (GCP) Redis and is now being uploaded to Azure Redis Cache.

Our Azure Redis Cache is deployed inside a private VNet, similar to our AKS setup, with a different subnet. However, the necessary VNet peering is configured.

As part of troubleshooting, we tried setting the storage account to public access, but the error persists.

The Managed Identity assigned to the storage account has all required permissions.

We also followed the troubleshooting steps suggested in the Azure portal but found no resolution.

Issue Details:

The error message is too generic and does not provide actionable insights.

Even after reviewing JSON error logs, no meaningful information is available.

This issue is blocking our project’s progress, and we need a resolution as soon as possible.

Request:

Could you provide guidance on additional troubleshooting steps or logs that can offer more insights into the failure? Is there any compatibility issue between GCP Redis RDB files and Azure Redis Cache that we should be aware of?

Looking forward to your assistance.Hello Microsoft Support Team,

We are encountering a critical issue while attempting to import an RDB file into our Azure Redis Cache instance (XXXXX-staging-redis). The request fails with a generic error message:

 Error: The request to import data into cache 'XXXXX-staging-redis' failed with status 'error' and no detailed error description provided.

Context:

The RDB file was exported from Google Cloud Platform (GCP) Redis and is now being uploaded to Azure Redis Cache.

Our Azure Redis Cache is deployed inside a private VNet, similar to our AKS setup, with a different subnet. However, the necessary VNet peering is configured.

As part of troubleshooting, we tried setting the storage account to public access, but the error persists.

The Managed Identity assigned to the storage account has all required permissions.

We also followed the troubleshooting steps suggested in the Azure portal but found no resolution.

Issue Details:

The error message is too generic and does not provide actionable insights.

Even after reviewing JSON error logs, no meaningful information is available.

This issue is blocking our project’s progress, and we need a resolution as soon as possible.

Request:

Could you provide guidance on additional troubleshooting steps or logs that can offer more insights into the failure? Is there any compatibility issue between GCP Redis RDB files and Azure Redis Cache that we should be aware of?

Looking forward to your assistance.
fyi json of error :  "level": "Informational",

    "operationId": "5a4b9a80-8f9d-4acd-a678-84551a3375ad",

    "operationName": {

        "value": "Microsoft.Cache/Redis/import/action",

        "localizedValue": "Import data into Redis from storage"

 "level": "Informational",

    "operationId": "5a4b9a80-8f9d-4acd-a678-84551a3375ad",

    "operationName": {

        "value": "Microsoft.Cache/Redis/import/action",

        "localizedValue": "Import data into Redis from storage"

 "level": "Informational",

    "operationId": "5a4b9a80xxxxxxx51a3375ad",

    "operationName": {

        "value": "Microsoft.Cache/Redis/import/action",

        "localizedValue": "Import data into Redis from storage"     "subStatus": {

        "value": "Accepted",

        "localizedValue": "Accepted (HTTP Status Code: 202)"

   "submissionTimestamp": "2025-05-13T04:12:17Z",

    "subscriptionId": "b3d9f02a-0xxxxxxceb6b8c02",

    "tenantId": "3a177a36-0499xxxxxxxx4068d286",

    "properties": {

        "statusCode": "Accepted",

        "serviceRequestId": null,

        "eventCategory": "Administrative",

        "entity": "/subscriptions/b30c8ceb6b8c02/resourceGroups/xxxxx-stage-rg-v2/providers/Microsoft.Cache/Redis/xxxx-stage-redis",

        "message": "Microsoft.Cache/Redis/import/action",

        "hierarchy": "3a177a36-0499-4937-8be0-d286/b3d9f02a-0138-0c8ceb6b8c02"

    },

    "relatedEvents": []

}

Answer 1

Hello shoyeb shaikh

As per Redis 7.0 release notes, Redis 7 uses a new version 10 format for RDB files, which is incompatible with older versions.

The cause of issue is RDB files are not backward compatible, meaning a file generated by Redis 7.0 cannot reliably be loaded by Redis 6.0.

Here are a few potential solutions you can consider:

1. Export from GCP using Redis 6.0

If possible, downgrade a Redis 6.0 instance on GCP, load your data into it, then export the RDB. This ensures compatibility.

2. Upgrade Azure Redis to 7.0

Redis 7.0 is available in Enterprise and Enterprise Flash tiers. If using Standard or Premium, consider upgrading the tier or region.

Also as per this document, while importing Data in Azure Redis, you can't import exported backups from newer Redis versions like Redis 6.0 into older versions like Redis 4.0.