Skip to content

Files

Latest commit

flang-msftflang-msft
fixed image links
Apr 1, 2022
33cd224 · Apr 1, 2022

History

History
71 lines (44 loc) · 3.81 KB

cache-how-to-active-geo-replication.md

File metadata and controls

71 lines (44 loc) · 3.81 KB
title description author ms.service ms.topic ms.date ms.author
Configure active geo-replication for Enterprise Azure Cache for Redis instances
Learn how to replicate your Azure Cache for Redis Enterprise instances across Azure regions
flang-msft
cache
conceptual
02/02/2022
franlanglois

Configure active geo-replication for Enterprise Azure Cache for Redis instances

In this article, you'll learn how to configure an active geo-replicated Azure Cache using the Azure portal.

Active geo-replication groups up to five Enterprise Azure Cache for Redis instances into a single cache that spans across Azure regions. All instances act as the local primaries. An application decides which instance or instances to use for read and write requests.

Note

Data transfer between Azure regions is charged at standard bandwidth rates.

Create or join an active geo-replication group

Important

Active geo-replication must be enabled at the time an Azure Cache for Redis is created.

  1. In the Advanced tab of New Redis Cache creation UI, select Enterprise for Clustering Policy.

    For more information on choosing Clustering policy, see Clustering Policy.

    :::image type="content" source="media/cache-how-to-active-geo-replication/cache-clustering-policy.png" alt-text="Configure active geo-replication":::

  2. Select Configure to set up Active geo-replication.

  3. Create a new replication group, for a first cache instance, or select an existing one from the list.

    :::image type="content" source="media/cache-how-to-active-geo-replication/cache-active-geo-replication-new-group.png" alt-text="Link caches":::

  4. Select Configure to finish.

    :::image type="content" source="media/cache-how-to-active-geo-replication/cache-active-geo-replication-configured.png" alt-text="Active geo-replication configured":::

  5. Wait for the first cache to be created successfully. Repeat the above steps for each cache instance in the geo-replication group.

Remove from an active geo-replication group

To remove a cache instance from an active geo-replication group, you just delete the instance. The remaining instances will reconfigure themselves automatically.

Force-unlink if there's a region outage

In case one of the caches in your replication group is unavailable due to region outage, you can forcefully remove the unavailable cache from the replication group.

You should remove the unavailable cache because the remaining caches in the replication group start storing the metadata that hasn’t been shared to the unavailable cache. When this happens, the available caches in your replication group might run out of memory.

  1. Go to Azure portal and select one of the caches in the replication group that is still available.

  2. Select to Active geo-replication in the Resource menu on the left to see the settings in the working pane. :::image type="content" source="media/cache-how-to-active-geo-replication/cache-active-geo-replication-group.png" alt-text="screenshot of active geo-replication group":::

  3. Select the cache that you need to force-unlink by checking the box.

  4. Select Force unlink and then OK to confirm. :::image type="content" source="media/cache-how-to-active-geo-replication/cache-cache-active-geo-replication-unlink.png" alt-text="screenshot of unlinking in active geo-replication":::

  5. Once the affected region's availability is restored, you need to delete the affected cache and recreate it to add it back to your replication group.

Next steps

Learn more about Azure Cache for Redis features.