Common Scenarios When Exporting/Importing Azure Redis Cache
Published Wednesday, August 17, 2022
Purpose
There are several reasons where users may fail to export / import Redis Cache data. To ease the troubleshooting process, this blog will follow the subsequent structure to introduce some possible causes and troubleshooting methods in detail.
- Scenarios
- Symptoms
- Possible Reasons
- Mitigation Methods
Possible causes when failed to export Redis Cache
Scenario 1: failed to export Redis Cache with “AuthorizationFailure” – (HTTP 403 at Redis Cache RP log)
Symptoms:
Error message: “The request to export data from cache ‘testexport’ failed with status ‘error’ and error ‘AuthorizationFailure: this request is not authorized to perform this operation’
Request ID: 05e9db08-301e-0068-3d64-a569cd000000
Time: 2022-08-01T05:09:34.7925950Z”.
Possible Reasons: target storage account has enabled firewall setting.
Mitigation Methods:
-
Option 1: disable storage firewall setting
-
Option 2: enable managed identity for existing Redis Cache: Enable Managed Identity . Choose either type of managed identity below to achieve the same goal (Note: managed identity functionality is only available in the Premium tier)
Scenario 2: conflict error when exporting Redis Cache – HTTP 409
Symptoms:
Error Message: "(Conflict) The resource '/subscription/xxx/resourceGroups/xxx/providers/Microsoft.Cache/Redis/testexport' is busy processing a previous update request or is undergoing system maintenance. As such, it is currently unable to accept the update request. Please try again later.
RequestID: 8e2a97e0-0c22-48c5-9e9a-b9554f61f83e"
Possible Reasons: multiple requests were sent to the same Redis Cache concurrently. The previous export job has not completed either due to long running job needs more time or stuck in the backend for some reasons.
Mitigation Methods:
- Option 1: retry after a while.
- Option 2: If the previous request stuck for long time and retry does not resolve the issue, open a support ticket for further investigation.
Scenario 3: BlobTypeNotSupported: Page blob is not supported for this account type.
Symptom:
Error message: “The request to export data from cache 'textexport' failed with status error and error 'BlobTypeNotSupported: Page blob is not supported for this account type.
RequestID: cd355d17-701e-007c-58e7-a66d23000000
Time:2022-08-03T03:17:31.8342062Z'”.
Possible Reasons: exporting Redis Cache works only with RDB files stored as page blobs and target storage account does not support page bob - Supported blob type when export Redis.
Mitigation Methods: use premium page blob account or normal standard general-purpose V2 account.
Possible causes when failed to import Redis Cache
Scenario 1: The request is not authorized to perform this operation – HTTP 403
Symptom:
Usually the Authorization Failure during import process consists of IP authorization(from local machine to target storage account) and authorization error(from target storage account to Redis Cache).
- Picture 1 - "The request is not authorized to perform this operation"
- Picture 2 - "The request to import data into cache 'testexport' failed with status 'error' and error"
Possible Reasons: target storage account has enabled firewall setting.
Mitigation Methods:
-
Option 1: disable target storage account firewall setting.
-
Option 2: Alternatively, whitelist the IP address and make use of managed identity to import Redis.
a. Go to Azure Portal and choose target storage account. From Networking panel, whitelist desired IP address.
b. Enable managed identity to import data when firewall setting is switched on (refer to the document for more details: Enable Managed Identity)
Scenario 2: conflict error when importing Redis Cache – HTTP 409
Symptoms:
Error Message: "(Conflict) The resource '/subscription/xxx/resourceGroups/xxx/providers/Microsoft.Cache/Redis/testexport' is busy processing a previous update request or is undergoing system maintenance. As such, it is currently unable to accept the update request. Please try again later.
RequestID: 9bda6421-f232-4a1d-8e03-02a17ee6659f"
Possible Reasons: multiple requests were sent to the same Redis Cache concurrently. The previous import job has not completed either due to long running job needs more time or stuck in the backend for some reasons.
Mitigation Methods:
- Option 1: retry after a while.
- Option 2: If the previous request stuck for long time and retry does not resolve the issue, open a support ticket for further investigation.
