Merge pull request #209974 from flang-msft/fxl---update/add-content-for-redis-6

fxl---upgrade redis 4 to 6

Author: denrea

articles/azure-cache-for-redis/TOC.yml

@@ -121,6 +121,8 @@
     items:
     - name: Choose a cache tier
       href: cache-overview.md#choosing-the-right-tier
+    - name: Upgrade to a new version
+      href: cache-how-to-upgrade.md
     - name: Set Redis version
       href: cache-how-to-version.md
     - name: Distribute your cache with clustering

articles/azure-cache-for-redis/cache-faq.yml

@@ -7,7 +7,7 @@ metadata:
   ms.author: franlanglois
   ms.service: cache
   ms.topic: faq
-  ms.date: 04/12/2022
+  ms.date: 09/08/2022
 
 title: Azure Cache for Redis FAQ
 summary: |
@@ -41,33 +41,22 @@ sections:
 
       - question: How do I know if a cache is affected? 
         answer: |
-          Affected caches fit into one of three groups: 
+          Please check Azure Advisor Recommendations. If your cache is affected, you see a recommendation in your subscription. 
 
-          - Caches using Classic Virtual Network (VNet) injection
+          :::image type="content" source="media/cache-faq/cache-advisor-upgrade.png" alt-text="Screenshot that Advisor recommendation to migrate cache from cloud services.":::
 
-             Any cache injected into a Classic VNet defaults to being built on Cloud Services.
 
-          - Caches in an Azure Resource Manager (ARM) VNet subnet that once contained a Cloud Services-based cache. 
-            
-             Once a Cloud Services-based cache is contained in a VNet subnet, all other caches in that subnet must also rely on Cloud Services 
-
-          -  Caches using geo-replication that were once replicated with a cache built on Cloud Services. 
-          
-               This case is rare, but there are a few caches that are use Cloud Services because they were originally geo-replicated with a Cloud Services-based cache.  
-        
-          Emails will go out to customers identifying the specific subscriptions and cache names affected. If you’d like to confirm whether your cache is affected, send an email to [[email protected]](mailto:[email protected]). 
-     
-      - question: What is the solution? 
+      - question: How do I migrate Cloud Services (classic) caches to Azure Virtual Machine Scale Sets? 
         answer: |
-          We have migrated most  caches from being built on Cloud Services (class) to being built on virtual machine scale sets. Migrating to virtual machine scale sets removes the dependency. There are two ways to initiate this process for caches in a VNet: 
+          We have migrated most  caches from being built on Cloud Services (class) to being built on Azure Virtual Machine Scale Sets. Migrating to Azure Virtual Machine Scale Sets removes the dependency. There are two ways to initiate this process for caches in a VNet: 
 
           - Migrate to a new cache using Private Links (recommended). 
 
              Create a new cache that uses Private Link for network isolation rather than VNet injection and [migrate your data to this cache](cache-vnet-migration.md). This option gives you the best and most secure network isolation experience, while also ensuring that all new caches are created using updated infrastructure. 
             
           - Migrate to a new cache in a new Azure Resource Manager VNet subnet.  
 
-             This option will fix the underlying dependency on Cloud Services while maintaining a similar VNet experience. We have migrated most caches from being built on Cloud Services (class) to being built on virtual machine scale sets. To migrate, delete the existing cache and create a new cache in a new Azure Resource Manager VNet subnet. For recommended options for migrating the data in the cache, see [Migrate to Azure Cache for Redis](cache-migration-guide.md).  
+             This option will fix the underlying dependency on Cloud Services while maintaining a similar VNet experience. We have migrated most caches from being built on Cloud Services (class) to being built on Azure Virtual Machine Scale Sets. To migrate, delete the existing cache and create a new cache in a new Azure Resource Manager VNet subnet. For recommended options for migrating the data in the cache, see [Migrate to Azure Cache for Redis](cache-migration-guide.md).  
 
       - question: My cache isn't using VNet injection, but I received notice that I need to migrate. What should I do? 
         answer: |

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

@@ -0,0 +1,74 @@
+---
+title: How to upgrade the Redis version of Azure Cache for Redis
+description: Learn how to upgrade the version of Azure Cache for Redis
+author: flang-msft
+
+ms.author: franlanglois
+ms.service: cache
+ms.topic: how-to
+ms.date: 09/08/2022
+ms.custom: template-how-to 
+---
+
+
+# How to upgrade an existing Redis 4 cache to Redis 6
+
+Azure Cache for Redis supports upgrading the version of your Azure Cache for Redis from Redis 4 to Redis 6. Upgrading is permanent, and it might cause a brief connection issue similar to regular monthly maintenance. As a precautionary step, we recommend exporting the data from your existing Redis 4 cache and testing your client application with a Redis 6 cache in a lower environment before upgrading.
+
+For more information, see [here](cache-how-to-import-export-data.md) for details on how to export.
+
+## Prerequisites
+
+- Azure subscription - [create one for free](https://azure.microsoft.com/free/)
+
+### Limitations
+
+- Upgrading a Basic tier cache results in brief unavailability and data loss.
+- Upgrading on geo-replicated cache isn't supported. You must manually unlink the cache instances before upgrading.
+- 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)](/azure/azure-cache-for-redis/cache-faq) for details on cloud services hosted caches.
+
+### Check the version of a cache
+
+Before you upgrade, check the Redis version of a cache by selecting **Properties** from the Resource menu of the Azure Cache for Redis. We recommend you use Redis 6.
+
+:::image type="content" source="media/cache-how-to-upgrade/cache-version-portal.png" alt-text="Screenshot of properties selected in the Resource menu.":::
+
+## Upgrade using the Azure portal
+
+1. In the Azure portal, select the Azure Cache for Redis instance that you want to upgrade from Redis 4 to Redis 6.
+
+1. On the left side of the screen, select **Advanced settings**.
+
+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.
+
+    :::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.":::
+
+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.
+
+    :::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.":::
+
+1. To check on the status of the upgrade, navigate to **Overview**.
+
+    :::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.":::
+
+## Upgrade using Azure CLI
+
+To upgrade a cache from 4 to 6 using the Azure CLI, use the following command:
+
+```azurecli-interactive
+az redis update --name cacheName --resource-group resourceGroupName --set redisVersion=6
+```
+
+## Upgrade using PowerShell
+
+To upgrade a cache from 4 to 6 using PowerShell, use the following command:
+
+```powershell-interactive
+Set-AzRedisCache -Name "CacheName" -ResourceGroupName "ResourceGroupName" -RedisVersion "6"
+```
+
+## Next steps
+
+- To learn more about Azure Cache for Redis versions, see lin[Set Redis version for Azure Cache for Redis](cache-how-to-version.md)
+- To learn more about Redis 6 features, see [Diving Into Redis 6.0 by Redis](https://redis.com/blog/diving-into-redis-6/)
+- To learn more about Azure Cache for Redis features: [Azure Cache for Redis Premium service tiers](cache-overview.md#service-tiers)

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

@@ -1,11 +1,12 @@
 ---
-title: Set Redis version for Azure Cache for Redis
-description: Learn how to configure Redis version
+title: Set the Redis version of Azure Cache for Redis
+description: Learn how to configure the version of Azure Cache for Redis
 author: flang-msft
+
 ms.author: franlanglois
 ms.service: cache
-ms.topic: conceptual
-ms.date: 06/03/2022
+ms.topic: how-to
+ms.date: 09/08/2022
 
 ---
 
@@ -14,14 +15,14 @@ ms.date: 06/03/2022
 In this article, you'll learn how to configure the Redis software version to be used with your cache instance. Azure Cache for Redis offers the latest major version of Redis and at least one previous version. It will update these versions regularly as newer Redis software is released. You can choose between the two available versions. Keep in mind that your cache will be upgraded to the next version automatically if the version it's using currently is no longer supported.
 
 > [!NOTE]
-> At this time, Redis 6 does not support ACL, and geo-replication between a Redis 4 and 6 cache.
+> At this time, Redis 6 does not support Access Control Lists (ACL) or geo-replication between a Redis 4 cache and Redis 6 cache.
 >
 
 ## Prerequisites
 
-* Azure subscription - [create one for free](https://azure.microsoft.com/free/)
+- Azure subscription - [create one for free](https://azure.microsoft.com/free/)
 
-## Create a cache using the Azure portal
+## How to create a cache using the Azure portal
 
 To create a cache, follow these steps:
 
@@ -35,9 +36,9 @@ To create a cache, follow these steps:
 
     | Setting      | Suggested value  | Description |
     | ------------ |  ------- | -------------------------------------------------- |
-    | **Subscription** | Select your subscription. | The subscription under which to create this new Azure Cache for Redis instance. | 
-    | **Resource group** | Select a resource group, or select **Create new** and enter a new resource group name. | Name for the resource group in which to create your cache and other resources. By putting all your app resources in one resource group, you can easily manage or delete them together. | 
-    | **DNS name** | Enter a globally unique name. | The cache name must be a string between 1 and 63 characters that contains only numbers, letters, or hyphens. The name must start and end with a number or letter, and can't contain consecutive hyphens. Your cache instance's *host name* will be *\<DNS name>.redis.cache.windows.net*. | 
+    | **Subscription** | Select your subscription. | The subscription under which to create this new Azure Cache for Redis instance. |
+    | **Resource group** | Select a resource group, or select **Create new** and enter a new resource group name. | Name for the resource group in which to create your cache and other resources. By putting all your app resources in one resource group, you can easily manage or delete them together. |
+    | **DNS name** | Enter a globally unique name. | The cache name must be a string between 1 and 63 characters that contains only numbers, letters, or hyphens. The name must start and end with a number or letter, and can't contain consecutive hyphens. Your cache instance's *host name* will be *\<DNS name>.redis.cache.windows.net*. |
     | **Location** | Select a location. | Select a [region](https://azure.microsoft.com/regions/) near other services that will use your cache. |
     | **Cache type** | Select a [cache tier and size](https://azure.microsoft.com/pricing/details/cache/). |  The pricing tier determines the size, performance, and features that are available for the cache. For more information, see [Azure Cache for Redis Overview](cache-overview.md). |
 
@@ -47,10 +48,12 @@ To create a cache, follow these steps:
 
 1. Select **Create**.
 
-    It takes a while for the cache to create. You can monitor progress on the Azure Cache for Redis **Overview** page. When **Status** shows as **Running**, the cache is ready to use.
+    It takes a while for the cache to be created. You can monitor progress on the Azure Cache for Redis **Overview** page. When **Status** shows as **Running**, the cache is ready to use.
 
 ## Create a cache using Azure PowerShell
 
+To create a cache using PowerShell:
+
 ```azurepowershell
     New-AzRedisCache -ResourceGroupName "ResourceGroupName" -Name "CacheName" -Location "West US 2" -Size 250MB -Sku "Standard" -RedisVersion "6"
 ```
@@ -59,11 +62,15 @@ For more information on how to manage Azure Cache for Redis with Azure PowerShel
 
 ## Create a cache using Azure CLI
 
+To create a cache using Azure CLI:
+
 ```azurecli-interactive
 az redis create --resource-group resourceGroupName --name cacheName --location westus2 --sku Standard --vm-size c0 --redisVersion="6"
 ```
+
 For more information on how to manage Azure Cache for Redis with Azure CLI, see [here](cli-samples.md)
 
+<!-- 
 ## Upgrade an existing Redis 4 cache to Redis 6
 
 Azure Cache for Redis supports upgrading your Redis cache server major version from Redis 4 to Redis 6. Upgrading is permanent and it might cause a brief connection blip. As a precautionary step, we recommend exporting the data from your existing Redis 4 cache and testing your client application with a Redis 6 cache in a lower environment before upgrading. For more information, see [here](cache-how-to-import-export-data.md) for details on how to export.
@@ -111,18 +118,28 @@ To upgrade a cache from 4 to 6 using PowerShell, use the following command:
 ```powershell-interactive
 Set-AzRedisCache -Name "CacheName" -ResourceGroupName "ResourceGroupName" -RedisVersion "6"
 ```
+ -->
+
+## How to check the version of a cache
+
+You can check the Redis version of a cache by selecting **Properties** from the Resource menu of the Azure Cache for Redis.
+
+:::image type="content" source="media/cache-how-to-version/cache-version-portal.png" alt-text="Screenshot of properties selected in the Resource menu.":::
 
 ## FAQ
 
 ### What features aren't supported with Redis 6?
 
-At this time, Redis 6 doesn't support ACL, and geo-replication between a Redis 4 and 6 cache.
+At this time, Redis 6 doesn't support Access Control Lists (ACL). Geo-replication between a Redis 4 cache and a Redis 6 cache is also not supported.
 
 ### Can I change the version of my cache after it's created?
 
-You can upgrade your existing Redis 4 caches to Redis 6, see [here](#upgrade-an-existing-redis-4-cache-to-redis-6) for details. Upgrading your cache instance is permanent and you cannot downgrade your Redis 6 caches to Redis 4 caches.
+You can upgrade your existing Redis 4 caches to Redis 6. Upgrading your cache instance is permanent and you can't downgrade your Redis 6 caches to Redis 4 caches.
+
+For more information, see [How to upgrade an existing Redis 4 cache to Redis 6](cache-how-to-upgrade.md).
 
 ## Next Steps
 
+- To learn more about upgrading your cache, see [How to upgrade an existing Redis 4 cache to Redis 6](cache-how-to-upgrade.md)
 - To learn more about Redis 6 features, see [Diving Into Redis 6.0 by Redis](https://redis.com/blog/diving-into-redis-6/)
 - To learn more about Azure Cache for Redis features: [Azure Cache for Redis Premium service tiers](cache-overview.md#service-tiers)