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/reliability/regions-multi-region-nonpaired.md
-16Lines changed: 0 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,10 +28,6 @@ To learn about how to create multi-region solutions by using Azure API Managemen
28
28
29
29
To learn about how to create multi-region solutions by using Azure App Service, see [Reliability in App Service](./reliability-app-service.md).
30
30
31
-
## Azure Blob Storage
32
-
33
-
To learn about how to create multi-region solutions using Azure Blob Storage, see [Reliability in Blob Storage](./reliability-storage-blob.md).
34
-
35
31
## Azure Cache for Redis
36
32
37
33
Azure Cache for Redis provides two distinct cross-region replication options: [active geo-replication](/azure/azure-cache-for-redis/cache-how-to-active-geo-replication) and [passive geo-replication](/azure/azure-cache-for-redis/cache-how-to-geo-replication). Neither option explicitly depends on region pairs.
@@ -65,10 +61,6 @@ To learn about how to create multi-region solutions by using Azure Data Factory,
65
61
66
62
For geo-replication of Azure Event Grid topics in nonpaired regions, you can implement [client-side failover](/azure/event-grid/custom-disaster-recovery-client-side).
67
63
68
-
## Azure Files
69
-
70
-
To learn about how to create multi-region solutions using Azure Files, see [Reliability in Azure Files](./reliability-storage-files.md).
71
-
72
64
## Azure IoT Hub
73
65
74
66
To learn about how to create multi-region solutions by using Azure IoT Hub, see [Reliability in IoT Hub](./reliability-iot-hub.md).
@@ -83,10 +75,6 @@ Log Analytics workspaces in Azure Monitor Logs don't use paired regions. To ensu
83
75
84
76
For more information, see [Enhance resilience by replicating your Log Analytics workspace across regions](/azure/azure-monitor/logs/workspace-replication).
85
77
86
-
## Azure Queue Storage
87
-
88
-
To learn about how to create multi-region solutions by using Azure Queue Storage, see [Reliability in Queue Storage](./reliability-storage-queue.md).
89
-
90
78
## Azure Service Bus
91
79
92
80
Azure Service Bus can provide regional resiliency, without a dependency on region pairs, by using either [geo-replication](/azure/service-bus-messaging/service-bus-geo-replication) or [geo-disaster recovery](/azure/service-bus-messaging/service-bus-geo-dr) features.
@@ -117,10 +105,6 @@ To achieve geo-replication in nonpaired regions:
117
105
118
106
-**For Azure Table Storage:** To learn about how to create multi-region solutions using Azure Table Storage, see [Reliability in Azure Table Storage](./reliability-storage-table.md).
119
107
120
-
## Azure Table Storage
121
-
122
-
To learn about how to create multi-region solutions using Azure Table Storage, see [Reliability in Azure Table Storage](./reliability-storage-table.md).
123
-
124
108
## Azure Virtual Desktop
125
109
126
110
For geo-replication in nonpaired regions for Azure Virtual Desktop, you need to consider session host VMs and storage for user profiles, applications, and data. Microsoft manages the Azure Virtual Desktop control plane, which is globally distributed and highly available.
0 commit comments