Import and Export data in Azure Cache for Redis

Use the import and export functionality in Azure Cache for Redis as a data management operation. You import data into your cache instance or export data from a cache instance using an Azure Cache for Redis Database (RDB) snapshot. The snapshots are imported or exported using a blob in an Azure Storage Account.

Import/Export is supported in the Premium tiers:

• Export - you can export your Azure Cache for Redis RDB snapshots to a Page Blob (Premium tier).
• Import - you can import your Azure Cache for Redis RDB snapshots from either a Page Blob or a Block Blob.

You can use Import/Export to migrate between different Azure Cache for Redis instances or populate the cache with data before use.

This article provides a guide for importing and exporting data with Azure Cache for Redis and provides the answers to commonly asked questions.

• Data is exported as an RDB page blob in the Premium tier.
• Caches running Redis 4.0 support RDB version 8 and below. Caches running Redis 6.0 support RDB version 9 and below.
• Exported backups from newer versions of Redis (for example, Redis 6.0) can't be imported into older versions of Redis (for example, Redis 4.0)

Use import to bring Redis compatible RDB files from any Redis server running in any cloud or environment, including Redis running on Linux, Windows, or any cloud provider such as Amazon Web Services and others. Importing data is an easy way to create a cache with prepopulated data. During the import process, Azure Cache for Redis loads the RDB files from Azure storage into memory and then inserts the keys into the cache.

1. To import one or more exported cache blobs, browse to your cache in the Azure portal and select Import data from the Resource menu. In the working pane, you see Choose Blob(s) where you can find RDB files.

   

2. Select Choose Blob(s) and select the storage account that contains the data to import.

   

3. Select the container that contains the data to import.

   

4. Select one or more blobs to import by selecting the area to the left of the blob name, and then Select.

   

5. Select Import to begin the import process.

   Important

   The cache is not accessible by cache clients during the import process, and any existing data in the cache is deleted.

   

   You can monitor the progress of the import operation by following the notifications from the Azure portal, or by viewing the events in the activity log.

   

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.

1. To export the current contents of the cache to storage, browse to your cache in the Azure portal and select Export data from the Resource menu. You see Choose Storage Container in the working pane.

   

2. Select Choose Storage Container and to display a list of available storage accounts. Select the storage account you want. The storage account must be in the same region as your cache. If you're using managed identity for authentication, the storage account can be in a different subscription. Otherwise, the storage account must be in the same subscription as your cache.

   Important

   • Export works with page blobs that are supported by both classic and Resource Manager storage accounts.
   • Azure Cache for Redis does not support exporting to ADLS Gen2 storage accounts.
   • Export is not supported by Blob storage accounts at this time.
   • If your cache data export to Firewall-enabled storage accounts fails, refer to What if I have firewall enabled on my storage account?

   For more information, see Azure storage account overview.

   

3. Choose the storage container you want to hold your export, then Select. If you want a new container, select Add Container to add it first, and then select it from the list.

   

4. Type a Blob name prefix and select Export to start the export process. The blob name prefix is used to prefix the names of files generated by this export operation.

   

   You can monitor the progress of the export operation by following the notifications from the Azure portal, or by viewing the events in the audit log.

   

   Caches remain available for use during the export process.

This section contains frequently asked questions about the Import/Export feature.

• Which tiers support Import/Export?
• Can I import data from any Redis server?
• What RDB versions can I import?
• Is my cache available during an Import/Export operation?
• Can I use Import/Export with Redis cluster?
• How does Import/Export work with a custom databases setting?
• How is Import/Export different from Redis persistence?
• Can I automate Import/Export using PowerShell, CLI, or other management clients?
• I received a timeout error during my Import/Export operation. What does it mean?
• I got an error when exporting my data to Azure Blob Storage. What happened?
• What if I have firewall enabled on my storage account?
• Can I import or export data from a storage account in a different subscription than my cache?
• Which permissions need to be granted to the storage account container shared access signature (SAS) token to allow export?

The import and export features are available only in the Premium tiers.

Yes, you can import data that was exported from Azure Cache for Redis instances. You can import RDB files from any Redis server running in any cloud or environment. The environments include Linux, Windows, or cloud providers such as Amazon Web Services. To do import this data, upload the RDB file from the Redis server you want into a page or block blob in an Azure Storage Account. Then, import it into your premium Azure Cache for Redis instance.

For example, you might want to:

1. Export the data from your production cache.

2. Then, import it into a cache that is used as part of a staging environment for testing or migration.

For more information on supported RDB versions used with import, see the compatibility section.

• Export - Caches remain available and you can continue to use your cache during an export operation.
• Import - Caches become unavailable when an import operation starts, and become available for use when the import operation completes.

Yes, and you can import/export between a clustered cache and a nonclustered cache. Since Redis cluster only supports database 0, any data in databases other than 0 isn't imported. When clustered cache data is imported, the keys are redistributed among the shards of the cluster.

Some pricing tiers have different databases limits, so there are some considerations when importing if you configured a custom value for the databases setting during cache creation.

• When importing to a pricing tier with a lower databases limit than the tier from which you exported:
  • If you're using the default number of databases, which is 16 for all pricing tiers, no data is lost.
  • If you're using a custom number of databases that falls within the limits for the tier to which you're importing, no data is lost.
  • If you're exported data contained data in a database that exceeds the limits of the new tier, the data from those higher databases isn't imported.

The Azure Cache for Redis persistence feature is primarily a data durability feature. Conversely, the import/export functionality is designed as a method to make periodic data backups for point-in-time recovery.

When persistence is configured, your cache persists a snapshot of the data to disk, based on a configurable backup frequency. The data is written with a Redis-proprietary binary format. If a catastrophic event occurs that disables both the primary and the replica caches, the cache data is restored automatically using the most recent snapshot.

Data persistence is designed for disaster recovery. It isn't intended as a point-in-time recovery mechanism.

• On the Premium tier, the data persistence file is stored in Azure Storage, but the file can't be imported into a different cache.

If you want to make periodic data backups for point-in-time recovery, we recommend using the import/export functionality. For more information, see How to configure data persistence for Azure Cache for Redis.

Yes, see the following instructions for the Premium tier:

• PowerShell instructions to import Redis data and to export Redis data.
• Azure CLI instructions to import Redis data and export Redis data

On the left, if you remain on Import data or Export data for longer than 15 minutes before starting the operation, you receive an error with an error message similar to the following example:

The request to import data into cache 'contoso55' failed with status 'error' and error 'One of the SAS URIs provided could not be used for the following reason: The SAS token end time (se) must be at least 1 hour from now and the start time (st), if given, must be at least 15 minutes in the past.

To resolve this error, start the import or export operation before 15 minutes has elapsed.

Export works only with RDB files stored as page blobs. Other blob types aren't currently supported, including Blob storage accounts with hot and cool tiers. For more information, see Azure storage account overview. If you're using an access key to authenticate a storage account, having firewall exceptions on the storage account tends to cause the import/export process to fail.

If using a Premium tier instance, you need to check “Allow Azure services on the trusted services list to access this storage account” in your storage account settings. Then, use managed identity (System or User assigned) and provision Storage Blob Data Contributor RBAC role for that object ID.

For more information, see managed identity for storage accounts - Azure Cache for Redis

In the Premium tier, you can import and export data from a storage account in a different subscription than your cache, but you must use managed identity as the authentication method. You will need to select the chosen subscription holding the storage account when configuring the import or export.

In order for export to an Azure storage account to work successfully, the shared access signature (SAS) token must have the following permissions:

• read
• add
• create
• write
• delete
• tag
• move

Learn more about Azure Cache for Redis features.

• Azure Cache for Redis service tiers