Skip to content

Commit adedeef

Browse files
authored
Merge pull request #259746 from Lakshmisha-KS/dataresidencynewnov29
Dataresidencynewnov29
2 parents 830d74a + 11f63ac commit adedeef

File tree

2 files changed

+4
-1
lines changed

2 files changed

+4
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ 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 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.
32+
Azure Data Manager for Energy stores and process customer data. By default, customer data is replicated to the [Azure paired regions](https://learn.microsoft.com/azure/reliability/cross-region-replication-azure#azure-paired-regions) for resiliency, but doesn't replicate or move data outside the geography in which the customer created the instance. In regions with requirement for data to remain within the sovereign geography, 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.
3333
3434
- name: Pricing and Billing
3535
questions:

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

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -51,9 +51,12 @@ Below is the list of primary and secondary regions for regions where disaster re
5151
|------------------|----------------------|------------------|
5252
|Americas | South Central US | North Central US |
5353
|Americas | East US | West US |
54+
|Americas | Brazil South* | |
5455
|Europe | North Europe | West Europe |
5556
|Europe | West Europe | North Europe |
5657

58+
(*) These regions are restricted in supporting customer scenarios for disaster recovery. For more information please contact your Microsoft sales or customer representatives.
59+
5760
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.
5861

5962
> [!IMPORTANT]

0 commit comments

Comments
 (0)