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/energy-data-services/concepts-tier-details.md
+9-4Lines changed: 9 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,13 +42,13 @@ The Standard tier of Azure Data Manager for energy is ideal for customers' produ
42
42
The standard tier is designed for production scenarios as it provides high availability, reliability and scale. The Standard tier includes the following:
43
43
44
44
* Availability Zones
45
-
* Disaster Recovery
45
+
* Disaster Recovery\*
46
46
* Financial Backed Service Level Agreement
47
47
* Higher Database Throughput
48
48
* Higher data partition maximum
49
49
* Higher support prioritization
50
50
51
-
51
+
(\*) Certain regions are restricted in supporting customer scenarios for disaster recovery. Please check the [Reliability in Azure Data Manager for Energy](reliability-energy-data-services.md) for more details on the regions which support disaster recovery.
52
52
53
53
## Tier details
54
54
| Features | Developer Tier | Standard Tier |
@@ -60,11 +60,16 @@ Support | Yes | Yes
60
60
Azure Customer Managed Encryption Keys|Yes| Yes
61
61
Azure Private Links|Yes| Yes
62
62
Financial Backed Service Level Agreement (SLA) Credits | No | Yes
63
-
Disaster Recovery |No| Yes
63
+
Disaster Recovery |No| Yes\*
64
64
Availability Zones |No| Yes
65
65
Database Throughput |Low| High
66
66
Included Data Partition | 1| 1
67
67
Maximum Data Partition |5 | 10
68
68
69
+
(\*) Certain regions are restricted in supporting customer scenarios for disaster recovery. Please check the [Reliability in Azure Data Manager for Energy](reliability-energy-data-services.md) for more details on the regions which support disaster recovery.
70
+
71
+
> [!IMPORTANT]
72
+
> Disaster recovery is currently not available in Brazil South region. For more information please contact your Microsoft sales or customer representative.
73
+
69
74
## How to participate
70
-
You can easily create a Developer tier resource by going to Azure Marketplace, [create portal](https://portal.azure.com/#create/Microsoft.AzureDataManagerforEnergy), and select your desired tier.
75
+
You can easily create a Developer tier resource by going to Azure Marketplace, [create portal](https://portal.azure.com/#create/Microsoft.AzureDataManagerforEnergy), and select your desired tier.
Copy file name to clipboardExpand all lines: articles/energy-data-services/faq-energy-data-services.yml
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -29,8 +29,8 @@ sections:
29
29
questions:
30
30
- question: Where does Azure Data Manager for Energy store customer data?
31
31
answer: >
32
-
Azure Data Manager for Energy stores/process customer data. By default, customer data is replicated to the paired region. For region with data residency requirements, customer data is always kept within the same region
33
-
32
+
Azure Data Manager for Energy stores/process customer data. By default, customer data is replicated to the other paired regions for resiliency, but Microsoft doesn't replicate or move data outside the geography. For region with data residency requirements, customer data is always kept within the same region. Please check the [Reliability in Azure Data Manager for Energy](reliability-energy-data-services.md) for more details on the regions which support disaster recovery and cross region data replication.
33
+
34
34
- name: Pricing and Billing
35
35
questions:
36
36
- question: Where can I learn about the pricing for Azure Data Manager for Energy?
Copy file name to clipboardExpand all lines: articles/energy-data-services/reliability-energy-data-services.md
+7-2Lines changed: 7 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,6 +29,7 @@ The Azure Data Manager for Energy supports availability zones in the following r
29
29
|------------------|----------------------|
30
30
| South Central US | North Europe |
31
31
| East US | West Europe |
32
+
| Brazil South ||
32
33
33
34
### Zone down experience
34
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.
@@ -41,7 +42,7 @@ Azure Data Manager for Energy is a regional service and, therefore, is susceptib
41
42
42
43
:::image type="content" source="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="media/reliability-energy-data-services/cross-region-disaster-recovery.png":::
43
44
44
-
Below is the list of primary and secondary regions:
45
+
Below is the list of primary and secondary regions for regions where disaster recovery is supported:
@@ -52,6 +53,10 @@ Below is the list of primary and secondary regions:
52
53
53
54
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](../storage/common/storage-redundancy.md#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 on-going ingestion job that isn't persisted yet is lost, and you must restart the ingestion process upon recovery.
54
55
56
+
> [!IMPORTANT]
57
+
> In the following regions, disaster recovery is not available. For more information please contact your Microsoft sales or customer representative.
58
+
> 1. Brazil South
59
+
55
60
#### Set up disaster recovery and outage detection
56
61
57
62
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.
@@ -72,4 +77,4 @@ If you [set up private links](how-to-set-up-private-links.md) to your Azure Data
72
77
73
78
## Next steps
74
79
> [!div class="nextstepaction"]
75
-
> [Reliability in Azure](../reliability/availability-zones-overview.md)
80
+
> [Reliability in Azure](../reliability/availability-zones-overview.md)
0 commit comments