Skip to content

Commit 7fdc0a2

Browse files
Merge pull request #243388 from flang-msft/fxl---Add-VNET-configuration-requirement-for-Redis-upgrade-
Fxl---add vnet configuration requirement for redis upgrade
2 parents 356312e + 13b77fc commit 7fdc0a2

File tree

1 file changed

+8
-5
lines changed

1 file changed

+8
-5
lines changed

articles/azure-cache-for-redis/cache-how-to-upgrade.md

Lines changed: 8 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: flang-msft
66
ms.author: franlanglois
77
ms.service: cache
88
ms.topic: how-to
9-
ms.date: 12/15/2022
9+
ms.date: 06/29/2023
1010
ms.custom: template-how-to, devx-track-azurecli
1111
---
1212

@@ -33,7 +33,10 @@ For more information on how to export, see [Import and Export data in Azure Cach
3333

3434
- When you upgrade a cache in the Basic tier, it's unavailable for several minutes and results in data loss.
3535
- Upgrading on geo-replicated cache isn't supported. You must manually unlink the cache instances before upgrading.
36-
- Upgrading a cache with a dependency on Cloud Services isn't supported. You should migrate your cache instance to Virtual Machine Scale Set before upgrading. For more information, see [Caches with a dependency on Cloud Services (classic)](./cache-faq.yml) for details on cloud services hosted caches.
36+
- Upgrading a cache with a dependency on Cloud Services isn't supported. You should migrate your cache instance to Virtual Machine Scale Set before upgrading.
37+
- For more information, see [Caches with a dependency on Cloud Services (classic)](./cache-faq.yml) for details on cloud services hosted caches.
38+
- When trying to upgrade to Redis 6, your VNet must be configured in accord with the requirements. Your upgrade might fail or the cache might not function properly after the upgrade if not configured correctly.
39+
- For more information on the VNet requirements, see [What are some common misconfiguration issues with Azure Cache for Redis and virtual networks](cache-how-to-premium-vnet.md#what-are-some-common-misconfiguration-issues-with-azure-cache-for-redis-and-virtual-networks).
3740

3841
### Check the version of a cache
3942

@@ -49,15 +52,15 @@ Before you upgrade, check the Redis version of a cache by selecting **Properties
4952

5053
1. If your cache instance is eligible to be upgraded, you should see the following blue banner. If you want to proceed, select the text in the banner.
5154

52-
:::image type="content" source="media/cache-how-to-upgrade/blue-banner-upgrade-cache.png" alt-text="Screenshot informing you that you can upgrade your cache to Redis 6 with additional features. Upgrading your cache instance cannot be reversed.":::
55+
:::image type="content" source="media/cache-how-to-upgrade/blue-banner-upgrade-cache.png" alt-text="Screenshot informing you that you can upgrade your cache to Redis 6 with more features. Upgrading your cache instance can't be reversed.":::
5356

5457
1. A dialog box displays a popup notifying you that upgrading is permanent and might cause a brief connection blip. Select **Yes** if you would like to upgrade your cache instance.
5558

5659
:::image type="content" source="media/cache-how-to-upgrade/dialog-version-upgrade.png" alt-text="Screenshot showing a dialog with more information about upgrading your cache with Yes selected.":::
5760

5861
1. To check on the status of the upgrade, navigate to **Overview**.
5962

60-
:::image type="content" source="media/cache-how-to-upgrade/upgrade-status.png" alt-text="Screenshot showing Overview in the Resource menu. Status shows cache is being upgraded.":::
63+
:::image type="content" source="media/cache-how-to-upgrade/upgrade-status.png" alt-text="Screenshot showing Overview in the Resource menu. Status shows cache is being upgraded.":::
6164

6265
## Upgrade using Azure CLI
6366

@@ -73,7 +76,7 @@ To upgrade a cache from 4 to 6 using PowerShell, use the following command:
7376

7477
```powershell-interactive
7578
Set-AzRedisCache -Name "CacheName" -ResourceGroupName "ResourceGroupName" -RedisVersion "6"
76-
```
79+
```
7780

7881
## Next steps
7982

0 commit comments

Comments
 (0)