Skip to content

Commit 0aed82b

Browse files
Merge pull request #251061 from Lakshmisha-KS/Brazilsouth
Brazilsouth
2 parents ec0fc47 + 8a6f18f commit 0aed82b

File tree

3 files changed

+18
-8
lines changed

3 files changed

+18
-8
lines changed

articles/energy-data-services/concepts-tier-details.md

Lines changed: 9 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -42,13 +42,13 @@ The Standard tier of Azure Data Manager for energy is ideal for customers' produ
4242
The standard tier is designed for production scenarios as it provides high availability, reliability and scale. The Standard tier includes the following:
4343

4444
* Availability Zones
45-
* Disaster Recovery
45+
* Disaster Recovery\*
4646
* Financial Backed Service Level Agreement
4747
* Higher Database Throughput
4848
* Higher data partition maximum
4949
* Higher support prioritization
5050

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.
5252

5353
## Tier details
5454
| Features | Developer Tier | Standard Tier |
@@ -60,11 +60,16 @@ Support | Yes | Yes
6060
Azure Customer Managed Encryption Keys|Yes| Yes
6161
Azure Private Links|Yes| Yes
6262
Financial Backed Service Level Agreement (SLA) Credits | No | Yes
63-
Disaster Recovery |No| Yes
63+
Disaster Recovery |No| Yes\*
6464
Availability Zones |No| Yes
6565
Database Throughput |Low| High
6666
Included Data Partition | 1| 1
6767
Maximum Data Partition |5 | 10
6868

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+
6974
## 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.

articles/energy-data-services/faq-energy-data-services.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -29,8 +29,8 @@ sections:
2929
questions:
3030
- question: Where does Azure Data Manager for Energy store customer data?
3131
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+
3434
- name: Pricing and Billing
3535
questions:
3636
- question: Where can I learn about the pricing for Azure Data Manager for Energy?

articles/energy-data-services/reliability-energy-data-services.md

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -29,6 +29,7 @@ The Azure Data Manager for Energy supports availability zones in the following r
2929
|------------------|----------------------|
3030
| South Central US | North Europe |
3131
| East US | West Europe |
32+
| Brazil South | |
3233

3334
### Zone down experience
3435
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
4142

4243
:::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":::
4344

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:
4546

4647
| Geography | Primary | Secondary |
4748
|------------------|----------------------|------------------|
@@ -52,6 +53,10 @@ Below is the list of primary and secondary regions:
5253

5354
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.
5455

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+
5560
#### Set up disaster recovery and outage detection
5661

5762
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
7277
7378
## Next steps
7479
> [!div class="nextstepaction"]
75-
> [Reliability in Azure](../reliability/availability-zones-overview.md)
80+
> [Reliability in Azure](../reliability/availability-zones-overview.md)

0 commit comments

Comments
 (0)