|
| 1 | +--- |
| 2 | +title: Reliability in Azure Data Manager for Energy |
| 3 | +description: Learn how to ensure energy data reliability with Azure Data Manager for Energy by using zone-redundant instances and active-passive disaster recovery. |
| 4 | +author: bharathim |
| 5 | +ms.author: bselvaraj |
| 6 | +ms.topic: reliability-article |
| 7 | +ms.service: azure-data-manager-energy |
| 8 | +ms.custom: references_regions |
| 9 | +ms.date: 06/07/2023 |
| 10 | +--- |
| 11 | + |
| 12 | + |
| 13 | +# Reliability in Azure Data Manager for Energy |
| 14 | + |
| 15 | +This article describes reliability support in [Azure Data Manager for Energy](/azure/energy-data-services/), and covers both regional resiliency with availability zones and cross-region resiliency with disaster recovery. For a more detailed overview of reliability in Azure, see [Azure reliability](/azure/well-architected/resiliency/overview). |
| 16 | + |
| 17 | +## Availability zone support |
| 18 | + |
| 19 | +[!INCLUDE [Availability zone description](~/reusable-content/ce-skilling/azure/includes/reliability/reliability-availability-zone-description-include.md)] |
| 20 | + |
| 21 | +Azure Data Manager for Energy supports zone-redundant instances by default and there's no additional configuration required. |
| 22 | + |
| 23 | +## Prerequisites |
| 24 | + |
| 25 | +The Azure Data Manager for Energy supports availability zones in the following regions: |
| 26 | + |
| 27 | +| Asia Pacific | Americas | Europe | Middle East/Africa | |
| 28 | +|-------------------|----------------------|----------------------|----------------------| |
| 29 | +| Australia East | Brazil South | North Europe | Qatar Central | |
| 30 | +| Central India | East US | Sweden Central | South Africa North | |
| 31 | +| Indonesia Central | South Central US | West Europe | UAE North | |
| 32 | +| Southeast Asia | | | | |
| 33 | + |
| 34 | +### Zone down experience |
| 35 | +During a zone-wide outage, no action is required during zone recovery. There may be a brief degradation of performance until the service self-heals and rebalances underlying capacity to adjust to healthy zones. During this period, you may experience 5xx errors and you may have to retry API calls until the service is restored. |
| 36 | + |
| 37 | +## Cross-region disaster recovery and business continuity |
| 38 | + |
| 39 | +[!INCLUDE [introduction to disaster recovery](~/reusable-content/ce-skilling/azure/includes/reliability/reliability-disaster-recovery-description-include.md)] |
| 40 | + |
| 41 | + |
| 42 | +### Disaster recovery in multi-region geography |
| 43 | + |
| 44 | +Azure Data Manager for Energy is a regional service and, therefore, is susceptible to region-down service failures. Azure Data Manager for Energy follows an active-passive failover configuration to recover from regional disaster. An active-passive configuration keeps warm Azure Data Manager for Energy resource running in the secondary region, but doesn't send traffic there unless the primary region fails. |
| 45 | + |
| 46 | +:::image type="content" source="/azure/energy-data-services/media/reliability-energy-data-services/cross-region-disaster-recovery.png" alt-text="Diagram of Azure data manager for energy cross region disaster recovery workflow." lightbox="/azure/energy-data-services/media/reliability-energy-data-services/cross-region-disaster-recovery.png"::: |
| 47 | + |
| 48 | +Below is the list of primary and secondary regions for regions where disaster recovery is supported: |
| 49 | + |
| 50 | +| Geography | Primary | Secondary | |
| 51 | +|--------------------|----------------------|-------------------| |
| 52 | +| Americas | Brazil South* | - | |
| 53 | +| Americas | East US | West US | |
| 54 | +| Americas | South Central US | North Central US | |
| 55 | +| Asia Pacific | Australia East | Australia Central | |
| 56 | +| Asia Pacific | Central India | South India | |
| 57 | +| Asia Pacific | Indonesia Central* | - | |
| 58 | +| Asia Pacific | Southeast Asia* | - | |
| 59 | +| Europe | North Europe | West Europe | |
| 60 | +| Europe | Sweden Central | Sweden South | |
| 61 | +| Europe | West Europe | North Europe | |
| 62 | +| Middle East/Africa | Qatar Central* | - | |
| 63 | +| Middle East/Africa | South Africa North | South Africa West | |
| 64 | +| Middle East/Africa | UAE North | UAE Central | |
| 65 | + |
| 66 | +(*) These regions are restricted in supporting customer scenarios for disaster recovery. For more information please contact your Microsoft sales or customer representatives. |
| 67 | + |
| 68 | +Azure Data Manager for Energy uses Azure Storage, Azure Cosmos DB and Elasticsearch index as underlying data stores for persisting your data partition data. These data stores offer high durability, availability, and scalability. Azure Data Manager for Energy uses [geo-zone-redundant storage](/azure/storage/common/storage-redundancy#geo-zone-redundant-storage) or GZRS to automatically replicate data to a secondary region that's hundreds of miles away from the primary region. The same security features enabled in the primary region (for example, encryption at rest using your encryption key) to protect your data are applicable to the secondary region. Similarly, Azure Cosmos DB is a globally distributed data service, which replicates the metadata (catalog) across regions. Elasticsearch index snapshots are taken at regular intervals and geo-replicated to the secondary region. All inflight data are ephemeral and therefore subject to loss. For example, in-transit data that is part of an ongoing ingestion job that isn't persisted yet is lost, and you must restart the ingestion process upon recovery. |
| 69 | + |
| 70 | +> [!IMPORTANT] |
| 71 | +> In the following regions, disaster recovery is not available. For more information please contact your Microsoft sales or customer representative. |
| 72 | +> - Brazil South |
| 73 | +> - Indonesia Central |
| 74 | +> - Qatar Central |
| 75 | +> - Southeast Asia |
| 76 | +
|
| 77 | +#### Set up disaster recovery and outage detection |
| 78 | + |
| 79 | +Azure Data Manager for Energy service continuously monitors service health in the primary region. If a hard service down failure is detected in the primary region, we attempt recovery before initiating failover to the secondary region on your behalf. We will notify you about the failover progress. Once the failover completes, you could connect to the Azure Data Manager for Energy resource in the secondary region and continue operations. However, there could be slight degradation in performance due to any capacity constraints in the secondary region. |
| 80 | + |
| 81 | +##### Managing the resources in your subscription |
| 82 | +You must handle the failover of your business apps connecting to Azure Data Manager for Energy resource and hosted in the same primary region. Additionally, you're responsible for recovering any diagnostic logs stored in your Log Analytics Workspace. |
| 83 | + |
| 84 | +If you [set up private links](/azure/energy-data-services/how-to-set-up-private-links) to your Azure Data Manager for Energy resource in the primary region, then you must create a secondary private endpoint to the same resource in the [paired region](/azure/reliability/regions-paired). |
| 85 | + |
| 86 | +> [!CAUTION] |
| 87 | +> If you don't enable public access networks or create a secondary private endpoint before an outage, you'll lose access to the failed over Azure Data Manager for Energy resource in the secondary region. You will be able to access the Azure Data Manager for Energy resource only after the primary region failback is complete. |
| 88 | + |
| 89 | +> [!IMPORTANT] |
| 90 | +> After failover and until the primary region failback completes, you will be unable to perform state modifications to Azure Data Manager for Energy resource created in your subscription. For example, |
| 91 | +> - you cannot **Enable** or **Disable** public access networks. |
| 92 | +> - you cannot **Approve** or **Reject** private endpoint connection to Azure Data Manager for Energy resource |
| 93 | +> - you cannot create a new data partition. |
| 94 | +
|
| 95 | +## Next steps |
| 96 | + |
| 97 | +- [Reliability in Azure](/azure/reliability/availability-zones-overview) |
0 commit comments