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/automation/how-to/move-account.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -133,4 +133,4 @@ When the move is complete, verify that the capabilities listed below are enabled
133
133
134
134
To learn how to move Automation to a new region, see [Move Automation account to another region](../../operational-excellence/relocation-automation.md).
135
135
136
-
To learn about moving resources in Azure, see [Move resources in Azure](../../azure-resource-manager/management/move-support-resources.md).
136
+
To learn about moving resources in Azure, see [Move resources in Azure](../../azure-resource-manager/management/move-support-resources.md).
Copy file name to clipboardExpand all lines: articles/reliability/migrate-monitor-log-analytics.md
+12-7Lines changed: 12 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,15 +11,17 @@ ms.subservice: logs
11
11
---
12
12
13
13
# Migrate Log Analytics Dedicated Cluster workspaces to availability zone support
14
-
15
-
This guide describes how to migrate dedicated cluster Log Analytics Dedicated Cluster workspaces from nonavailability zone support to availability support.
14
+
15
+
This guide describes how to migrate dedicated cluster Log Analytics Dedicated Cluster workspaces from non-availability zone support to availability support.
16
16
17
17
> [!NOTE]
18
18
> Application Insights resources can also use availability zones, but only if they are workspace-based and the workspace uses a dedicated cluster. Classic (non-workspace-based) Application Insights resources cannot use availability zones.
19
19
20
+
20
21
## Prerequisites
21
22
22
-
- This article applies to workspaces that use dedicated clusters. If your workspace isn’t using a dedicated cluster, it’s using a shared cluster, which is managed by the Log Analytics service. In regions that have availability zones, shared clusters use availability zones or are being migrated to use them. For more information, see [Log Analytics - Supported regions](/azure/azure-monitor/logs/availability-zones#supported-regions).
23
+
- This article applies to workspaces that use dedicated clusters. If your workspace isn’t using a dedicated cluster, it’s using a shared cluster, which is managed by the Log Analytics service. In regions that have availability zones, shared clusters use availability zones or are being migrated to use them. For more details, see [Log Analytics - Supported regions](/azure/azure-monitor/logs/availability-zones#supported-regions).
24
+
23
25
- Make sure that the region to which you wish to move is a region that supports availability zones. To see which regions support availability zones, see [supported regions](/azure/azure-monitor/logs/availability-zones#supported-regions).
24
26
25
27
## Downtime requirements
@@ -41,19 +43,22 @@ Move your workspace to an availability zone by [creating a new dedicated cluster
41
43
42
44
Transitioning to a new cluster can be a gradual process. Don't remove the previous cluster until it is purged of any data. For example, if your workspace retention is set 60 days, you may want to keep your old cluster running for that period before removing it.
43
45
44
-
Any queries against your workspace query both clusters as required to provide you with a single, unified result set. As a result, all Azure Monitor features that rely on the workspace, such as workbooks and dashboards, continue to receive the full, unified result set based on data from both clusters.
46
+
Any queries against your workspace queries both clusters as required to provide you with a single, unified result set. As a result, all Azure Monitor features that rely on the workspace, such as workbooks and dashboards, continue to receive the full, unified result set based on data from both clusters.
45
47
46
48
## Billing
47
-
48
49
[Dedicated clusters](/azure/azure-monitor/logs/logs-dedicated-clusters#create-a-dedicated-cluster) require a commitment tier starting at 100 GB per day.
49
50
50
-
The new cluster isn’t billed during its first day to avoid double billing during configuration. Only the data ingested before the migration completes would still be billed on the date of migration.
51
+
The new cluster isn’t billed during its first day to avoid double billing during configuration. Only the data ingested before the migration completes would still be billed on the date of migration.
52
+
51
53
52
54
## Related content
53
55
54
56
Learn more about:
55
57
56
-
-[Relocate Log Analytics workspaces to another region](../azure-resource-manager/management/relocation/relocation-log-analytics.md)
58
+
-[Relocate Log Analytics workspaces to another region](../operational-excellence/relocation-log-analytics.md)
Copy file name to clipboardExpand all lines: articles/reliability/reliability-event-grid.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -45,9 +45,9 @@ Because Event Grid supports availability zones automatically in regions that sup
45
45
46
46
If you relocate your Event Grid resources to a region that supports availability zones, you automatically receive availability zone support. To learn how to relocate your resources to another region that supports availability zones, see the following:
47
47
48
-
-[Relocate Azure Event Grid system topics to another region](../azure-resource-manager/management/relocation/relocation-event-grid-system-topics.md)
49
-
-[Relocate Azure Event Grid custom topics to another region](../azure-resource-manager/management/relocation/relocation-event-grid-custom-topics.md)
50
-
-[Relocate Azure Event Grid domains to another region](../azure-resource-manager/management/relocation/relocation-event-grid-domains.md)
48
+
-[Relocate Azure Event Grid system topics to another region](../operational-excellence/relocation-event-grid-system-topics.md)
49
+
-[Relocate Azure Event Grid custom topics to another region](../operational-excellence/relocation-event-grid-custom-topics.md)
50
+
-[Relocate Azure Event Grid domains to another region](../operational-excellence/relocation-event-grid-domains.md)
51
51
52
52
## Cross-region disaster recovery and business continuity
Copy file name to clipboardExpand all lines: articles/reliability/reliability-event-hubs.md
+23-11Lines changed: 23 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,52 +11,64 @@ ms.date: 03/31/2025
11
11
12
12
<!--#Customer intent: I want to understand reliability support in Azure Event Hubs so that I can respond to and/or avoid failures in order to minimize downtime and data loss. -->
13
13
14
+
14
15
# Reliability in Azure Event Hubs
15
16
16
17
This article describes reliability support in [Azure Event Hubs](../event-hubs/event-hubs-about.md), and covers both intra-regional resiliency with [availability zones](#availability-zone-support) and [cross-region disaster recovery and business continuity](#cross-region-disaster-recovery-and-business-continuity). For a more detailed overview of reliability principles in Azure, see [Azure reliability](/azure/architecture/framework/resiliency/overview).
17
18
19
+
18
20
## Availability zone support
19
21
20
22
[!INCLUDE [Availability zone description](includes/reliability-availability-zone-description-include.md)]
21
23
22
-
Event Hubs implements transparent failure detection and failover mechanisms so that, when failure occurs, the service continues to operate within the assured service-levels and without noticeable interruptions. If you create an Event Hubs namespace in a region that supports availability zones, [zone redundancy](./availability-zones-overview.md#zonal-and-zone-redundant-services) is automatically enabled. With zone-redundancy, fault tolerance is increased and the service has enough capacity reserves to cope with the outage of an entire facility. Both metadata and data (events) are replicated across data centers in each zone.
24
+
25
+
Event Hubs implements transparent failure detection and failover mechanisms so that, when failure occurs, the service continues to operate within the assured service-levels and without noticeable interruptions. If you create an Event Hubs namespace in a region that supports availability zones, [zone redundancy](./availability-zones-overview.md#zonal-and-zone-redundant-services) is automatically enabled. With zone-redundancy, fault tolerance is increased and the service has enough capacity reserves to cope with the outage of an entire facility. Both metadata and data (events) are replicated across data centers in each zone.
26
+
23
27
24
28
### Prerequisites
25
29
26
-
Availability zone support is only available in [Azure regions with availability zones](./regions-list.md).
30
+
Availability zone support is only available in [Azure regions with availability zones](./regions-list.md).
31
+
27
32
28
33
### Create a resource with availability zones enabled
29
34
30
-
When you use the Azure portal, zone redundancy is automatically enabled. When you create a namespace, you see the following highlighted message when you select a region that supports availability zones.
35
+
When you use the Azure portal, zone redundancy is automatically enabled. When you create a namespace, you see the following highlighted message when you select a region that supports availability zones.
31
36
32
37
:::image type="content" source="../event-hubs/media/event-hubs-geo-dr/eh-az.png" alt-text="Screenshot showing the Create Namespace page with a region that has availability zones.":::
33
38
39
+
34
40
### Availability zone migration
35
41
36
-
When you create availability zones in a region that supports them, availability zones are automatically enabled. If you wish to learn how to move your Event Hubs namespace to a new region that supports availability zones, see [Relocate Event Hubs to another region](../azure-resource-manager/management/relocation/relocation-event-hub.md).
42
+
When you create availability zones in a region that supports them, availability zones are automatically enabled. If you wish to learn how to move your Event Hubs namespace to a new region that supports availability zones, see
43
+
[Relocate Event Hubs to another region](../operational-excellence/relocation-event-hub.md).
44
+
37
45
38
46
## Cross-region disaster recovery and business continuity
39
47
40
48
[!INCLUDE [introduction to disaster recovery](includes/reliability-disaster-recovery-description-include.md)]
41
49
42
-
The all-active Azure Event Hubs cluster model with availability zone support provides resiliency against hardware and datacenter outages. However, if a disaster where an entire region and all zones are unavailable, you can use Geo-disaster recovery to recover your workload and application configuration.
50
+
The all-active Azure Event Hubs cluster model with availability zone support provides resiliency against hardware and datacenter outages. However, if a disaster where an entire region and all zones are unavailable, you can use Geo-disaster recovery to recover your workload and application configuration.
43
51
44
52
There are two features that provide geo-disaster recovery in Azure Event Hubs.
45
53
46
54
-**Geo-disaster recovery (Metadata DR)**, which just provides replication of only metadata.
47
55
48
-
Geo-Disaster recovery ensures that the entire configuration of a namespace (Event Hubs, Consumer Groups, and settings) is continuously replicated from a primary namespace to a secondary namespace when paired.
49
-
56
+
57
+
Geo-Disaster recovery ensures that the entire configuration of a namespace (Event Hubs, Consumer Groups, and settings) is continuously replicated from a primary namespace to a secondary namespace when paired.
58
+
50
59
The Geo-disaster recovery feature of Azure Event Hubs is a disaster recovery solution. The concepts and workflow described in this article apply to disaster scenarios, and not to temporary outages. For a detailed discussion of disaster recovery in Microsoft Azure, see [this article](/azure/architecture/resiliency/disaster-recovery-azure-applications).
51
-
52
-
With Geo-Disaster recovery, you can initiate a once-only failover move from the primary to the secondary at any time. The failover move points the chosen alias name for the namespace to the secondary namespace. After the move, the pairing is then removed. The failover is nearly instantaneous once initiated.
60
+
61
+
With Geo-Disaster recovery, you can initiate a once-only failover move from the primary to the secondary at any time. The failover move points the chosen alias name for the namespace to the secondary namespace. After the move, the pairing is then removed. The failover is nearly instantaneous once initiated.
53
62
54
63
For detailed information, samples, and further documentation, on Geo-Disaster recovery in Event Hubs, see [Azure Event Hubs - Geo-disaster recovery](../event-hubs/event-hubs-geo-dr.md).
55
64
56
65
-**Geo-replication (public preview)**, which provides replication of both metadata and data, replicates configuration information and all of the data from a primary namespace to one, or more secondary namespaces. When a failover is performed, the selected secondary becomes the primary and the previous primary becomes a secondary. Users can perform a failover back to the original primary when desired.
57
66
58
-
For detailed information, samples, and further documentation, on Geo-replication in Event Hubs, see [Geo-replication](../event-hubs/geo-replication.md).
67
+
For detailed information, samples, and further documentation, on Geo-replication in Event Hubs, see [Geo-replication ](../event-hubs/geo-replication.md).
0 commit comments