Merge pull request #299731 from flang-msft/fxl---address-high-availability-items

JamesJBarnett · web-flow · commit bb0937dd3180 · 2025-05-12T16:18:40.000-07:00
fxl---remove bogus information
diff --git a/articles/redis/TOC.yml b/articles/redis/TOC.yml
@@ -22,7 +22,7 @@ items:
         href: how-to-manage-redis-cache-powershell.md
       - name: Create and manage with Azure CLI
         href: scripts/create-manage-cache.md
-      - name: Create and manage premium cache with Azure CLI
+      - name: Create and manage a premium cache with Azure CLI
         href: ../azure-cache-for-redis/scripts/create-manage-premium-cache-cluster.md
       - name: Create Redis cache - Bicep
         displayName: ARM, Resource Manager, Template
@@ -67,8 +67,6 @@ items:
       href: how-to-upgrade.md
     - name: Save with reservations 
       href: reserved-pricing.md
-    - name: Migrate to Azure Redis from other caches
-      href: /migrate/migration-guide.md
     - name: Planning FAQs
       href: planning-faq.yml
     - name: Redis modules 
@@ -171,12 +169,8 @@ items:
       href: how-to-persistence.md
     - name: Set up Enterprise active geo-replication
       href: how-to-active-geo-replication.md
-    - name: Configure your cache for high availability
-      href: high-availability.md
     - name: Failover and patching
       href: failover.md
-    - name: Migrate to availability zone support
-      href: ../reliability/migrate-cache-redis.md
 
   - name: Diagnose and troubleshoot
     items:
diff --git a/articles/redis/how-to-manage-redis-cache-powershell.md b/articles/redis/how-to-manage-redis-cache-powershell.md
@@ -535,4 +535,3 @@ For more information about Microsoft Azure Germany, see [Microsoft Azure Germany
 * [Azure Cache for Redis cmdlets](/powershell/module/az.rediscache)
 * [Azure PowerShell cmdlets](/powershell/module/)
 * [PowerShell Community blog](https://devblogs.microsoft.com/powershell-community/)
-
diff --git a/articles/redis/migrate/migration-guide.md b/articles/redis/migrate/migration-guide.md
@@ -24,7 +24,7 @@ Open-source Redis can run in many compute environments. Common examples include:
 - **Cloud-based VMs** - Redis caches running on Azure VMs, AWS EC2, and so on.
 - **Hosting services** - Managed Redis services such as AWS ElastiCache.
 
-If you have such a cache, you may be able to move it to Azure Managed Redis with minimal interruption or downtime. 
+If you have such a cache, you may be able to move it to Azure Managed Redis with minimal interruption or downtime.
 
 If you're looking to move from one Azure region to another, you [Move Azure Managed Redis instances to different regions](../../azure-cache-for-redis/cache-moving-resources.md).
 
@@ -35,9 +35,9 @@ There are different ways that you can switch from one cache to another. Dependin
    | Option       | Advantages | Disadvantages |
    | ------------ | ---------- | ------------- |
    | Create a new cache | Simplest to implement. | Need to repopulate data to the new cache, which may not work with many applications. |
-   | Export and import data via RDB file | Compatible with any Redis cache generally. | Some data could be lost, if they're written to the existing cache after the RDB file is generated. | 
-   | Dual-write data to two caches | No data loss or downtime. Uninterrupted operations of the existing cache. Easier testing of the new cache. | Needs two caches for an extended period of time. | 
-   | Migrate data programmatically | Full control over how data are moved. | Requires custom code. | 
+   | Export and import data via RDB file | Compatible with any Redis cache generally. | Some data could be lost, if they're written to the existing cache after the RDB file is generated. |
+   | Dual-write data to two caches | No data loss or downtime. Uninterrupted operations of the existing cache. Easier testing of the new cache. | Needs two caches for an extended period of time. |
+   | Migrate data programmatically | Full control over how data are moved. | Requires custom code. |
 
 ### Create a new Azure Managed Redis
 
@@ -47,9 +47,9 @@ General steps to implement this option are:
 
 1. Create a new Azure Managed Redis instance.
 
-2. Update your application to use the new instance.
+1. Update your application to use the new instance.
 
-3. Delete the old Redis instance.
+1. Delete the old Redis instance.
 
 ### Export data to an RDB file and import it into Azure Managed Redis
 
@@ -61,36 +61,35 @@ Open-source Redis defines a standard mechanism for taking a snapshot of a cache'
 
 General steps to implement this option are:
 
-<!-- cawa - remove reference to premium tier -->
-1. Create a new Azure Managed Redis instance in the premium tier that is the same size as (or bigger than) the existing cache.
+1. Create a new Azure Managed Redis instance that is the same size as (or bigger than) the existing cache.
 
-2. Save a snapshot of the existing Redis cache. You can [configure Redis to save snapshots](https://redis.io/topics/persistence) periodically, or run the process manually using the [SAVE](https://redis.io/commands/save) or [BGSAVE](https://redis.io/commands/bgsave) commands. The RDB file is named “dump.rdb” by default and will be located at the path specified in the *redis.conf* configuration file.
+1. Save a snapshot of the existing Redis cache. You can [configure Redis to save snapshots](https://redis.io/topics/persistence) periodically, or run the process manually using the [SAVE](https://redis.io/commands/save) or [BGSAVE](https://redis.io/commands/bgsave) commands. The RDB file is named “dump.rdb” by default and will be located at the path specified in the *redis.conf* configuration file.
 
     > [!NOTE]
     > If you’re migrating data within Azure Managed Redis, see [these instructions on how to export an RDB file](../how-to-import-export-data.md) or use the [PowerShell Export cmdlet](/powershell/module/az.rediscache/export-azrediscache) instead.
     >
 
-3. Copy the RDB file to an Azure storage account in the region where your new cache is located. You can use AzCopy for this task.
+1. Copy the RDB file to an Azure storage account in the region where your new cache is located. You can use AzCopy for this task.
 
-4. Import the RDB file into the new cache using these [import instructions](../how-to-import-export-data.md) or the [PowerShell Import cmdlet](/powershell/module/az.rediscache/import-azrediscache).
+1. Import the RDB file into the new cache using these [import instructions](../how-to-import-export-data.md) or the [PowerShell Import cmdlet](/powershell/module/az.rediscache/import-azrediscache).
 
-5. Update your application to use the new cache instance.
+1. Update your application to use the new cache instance.
 
 ### Write to two Redis caches simultaneously during migration period
 
 Rather than moving data directly between caches, you may use your application to write data to both an existing cache and a new one you're setting up. The application will still read data from the existing cache initially. When the new cache has the necessary data, you switch the application to that cache and retire the old one. Let's say, for example, you use Redis as a session store and the application sessions are valid for seven days. After writing to the two caches for a week, you'll be certain the new cache contains all non-expired session information. You can safely rely on it from that point onward without concern over data loss.
 
 General steps to implement this option are:
 
-1. Create a new Azure Managed Redis instance in the premium tier that is the same size as (or bigger than) the existing cache.
+1. Create a new Azure Managed Redis instance that is the same size as (or bigger than) the existing cache.
 
-2. Modify application code to write to both the new and the original instances.
+1. Modify application code to write to both the new and the original instances.
 
-3. Continue reading data from the original instance until the new instance is sufficiently populated with data.
+1. Continue reading data from the original instance until the new instance is sufficiently populated with data.
 
-4. Update the application code to reading and writing from the new instance only.
+1. Update the application code to reading and writing from the new instance only.
 
-5. Delete the original instance.
+1. Delete the original instance.
 
 ### Migrate programmatically
 
@@ -104,15 +103,15 @@ General steps to implement this option are:
 
 1. Create a VM in the region where the existing cache is located. If your dataset is large, choose a relatively powerful VM to reduce copying time.
 
-2. Create a new Azure Managed Redis instance.
+1. Create a new Azure Managed Redis instance.
 
-3. Flush data from the new cache to ensure that it's empty. This step is required because the copy tool itself doesn't overwrite any existing key in the target cache.
+1. Flush data from the new cache to ensure that it's empty. This step is required because the copy tool itself doesn't overwrite any existing key in the target cache.
 
     > [!IMPORTANT]
     > Make sure to NOT flush from the source cache.
     >
 
-4. Use an application such as the open-source tool above to automate the copying of data from the source cache to the target. Remember that the copy process could take a while to complete depending on the size of your dataset.
+1. Use an application such as the open-source tool above to automate the copying of data from the source cache to the target. Remember that the copy process could take a while to complete depending on the size of your dataset.
 
 ## Related content
 
