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
+3-5Lines changed: 3 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -81,8 +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 should not have the dependency on Cloud Services (classic).
85
-
<!-- @msfteegarden - Not sure what 'should' means. Don't choose it< or afterwards check that it doesn't? -->
84
+
The new pair of geo-replicated caches will not have the same dependency on Cloud Services.
86
85
87
86
- question: What happens if caches aren't upgraded/migrated by August 31, 2024?
88
87
answer: |
@@ -103,10 +102,9 @@ sections:
103
102
01. _Inactive Stage_ (January 1, 2024 to August 31, 2024)
104
103
105
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.
106
-
107
-
108
-
![./media/cache-cloud-service-timeline.png]
109
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
+
110
108
111
109
- question: Where can I get more information if I have more questions about this retirement?
0 commit comments