You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-cache-for-redis/cache-faq.yml
+7-8Lines changed: 7 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -55,21 +55,21 @@ sections:
55
55
56
56
- Caches using geo-replication that were once replicated with a cache built on Cloud Services.
57
57
58
-
This case is rare, but there are a few caches that are pinned to Cloud Services because they were originally geo-replicated with a Cloud Services-based cache.
58
+
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.
59
59
60
60
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]).
61
61
62
62
- question: What is the solution?
63
63
answer: |
64
-
We have migrated most caches from being built on Cloud Services (class) to being built on Virtual Machine Scale Sets (VMSS). Migrating to VMSS removes the dependency. There are two ways to initiate this process for caches in a VNet:
64
+
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:
65
65
66
66
- Migrate to a new cache using Private Links (recommended).
67
67
68
68
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.
69
69
70
-
- Migrate to a new cache in a new ARM VNet subnet.
70
+
- Migrate to a new cache in a new Azure Resource Manager VNet subnet.
71
71
72
-
This option will fix the underlying dependency on Cloud Services while maintaining a similar VNet experience. We hae migrated most caches from being built on Cloud Services (class) to being built on Virtual machine Scale Sets (VMSS). To migrate, delete the existing cache and create a new cache in a new ARM VNET subnet. For recommended options for migrating the data in the cache, see [Migrate to Azure Cache for Redis](cache-migration-guide.md).
72
+
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).
73
73
74
74
- question: My cache isn't using VNet injection, but I received notice that I need to migrate. What should I do?
75
75
answer: |
@@ -81,7 +81,7 @@ sections:
81
81
1. Unlink your original pair of geo-replicated caches and [export an RDB file](cache-how-to-import-export-data.md#export) from the primary cache.
82
82
1. [Import the RDB](cache-how-to-import-export-data.md#import) file into the primary cache in your new geo-replicated pair.
83
83
84
-
The new pair of geo-replicated caches will not have the same dependency on Cloud Services.
84
+
The new pair of geo-replicated caches won't have the same dependency on Cloud Services.
85
85
86
86
- question: What happens if caches aren't upgraded/migrated by August 31, 2024?
87
87
answer: |
@@ -103,12 +103,11 @@ sections:
103
103
104
104
Caches will only receive critical security fixes. All customers with support issues will be requested to migrate to a VMSS-based cache before receiving support. Customers must move off their caches by August 31, 2024.
105
105
106
-
:::image type="content" source="/media/cache-cloud-service-timeline.png" alt-text="picture of a timeline that shows the timeline for retiring cloud services (classic).":::
107
-
106
+
:::image type="content" source="media/cache-faq/cache-cloud-service-timeline.png" alt-text="picture of a timeline that shows the timeline for retiring cloud services (classic).":::
108
107
109
108
- question: Where can I get more information if I have more questions about this retirement?
110
109
answer: |
111
-
Post any of your questions to the [Q&A page](https://aka.ms/redisretirementquestions) for Cloud Services (classic) retirement. Also, You can can send email to [[email protected]](mailto:[email protected]) for more information.
110
+
Post any of your questions to the [Q&A page](https://aka.ms/redisretirementquestions) for Cloud Services (classic) retirement. Also, You can send email to [[email protected]](mailto:[email protected]) for more information.
0 commit comments