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/postgresql/flexible-server/concepts-geo-disaster-recovery.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
@@ -17,7 +17,7 @@ ms.date: 10/23/2023
17
17
18
18
If there's a region-wide disaster, Azure can provide protection from regional or large geography disasters with disaster recovery by making use of another region. For more information on Azure disaster recovery architecture, see [Azure to Azure disaster recovery architecture](../../site-recovery/azure-to-azure-architecture.md).
19
19
20
-
Azure Database for MySQL flexible server provides features that protect data and mitigates downtime for your mission-critical databases during planned and unplanned downtime events. Built on top of the Azure infrastructure that offers robust resiliency and availability, Azure Database for MySQL flexible server offers business continuity features that provide fault-protection, address recovery time requirements, and reduce data loss exposure. As you architect your applications, you should consider the downtime tolerance - the recovery time objective (RTO), and data loss exposure - the recovery point objective (RPO). For example, your business-critical database requires stricter uptime than a test database.
20
+
Azure Database for PostgreSQL flexible server provides features that protect data and mitigates downtime for your mission-critical databases during planned and unplanned downtime events. Built on top of the Azure infrastructure that offers robust resiliency and availability, Azure Database for PostgreSQL flexible server offers business continuity features that provide fault-protection, address recovery time requirements, and reduce data loss exposure. As you architect your applications, you should consider the downtime tolerance - the recovery time objective (RTO), and data loss exposure - the recovery point objective (RPO). For example, your business-critical database requires stricter uptime than a test database.
21
21
22
22
## Compare geo-replication with geo-redundant backup storage
23
23
Both geo-replication with read replicas and geo-backup are solutions for geo-disaster recovery. However, they differ in the details of their offerings. To choose the right solution for your system, it's important to understand and compare their features.
@@ -43,7 +43,7 @@ For more information on geo-redundant backup and restore, see [geo-redundant bac
43
43
44
44
## Read replicas
45
45
46
-
Cross region read replicas can be deployed to protect your databases from region-level failures. Read replicas are updated asynchronously using Azure Database for MySQL flexible server's physical replication technology, and can lag the primary. Read replicas are supported in general purpose and memory optimized compute tiers.
46
+
Cross region read replicas can be deployed to protect your databases from region-level failures. Read replicas are updated asynchronously using Azure Database for PostgreSQL flexible server's physical replication technology, and can lag the primary. Read replicas are supported in general purpose and memory optimized compute tiers.
47
47
48
48
For more information on read replica features and considerations, see [Read replicas](/azure/postgresql/flexible-server/concepts-read-replicas).
49
49
@@ -58,7 +58,7 @@ For more information on unplanned downtime mitigation and recovery after regiona
58
58
## Next steps
59
59
60
60
> [!div class="nextstepaction"]
61
-
> [Azure Database for MySQL flexible server documentation](/azure/postgresql/)
61
+
> [Azure Database for PostgreSQL flexible server documentation](/azure/postgresql/)
62
62
63
63
> [!div class="nextstepaction"]
64
64
> [Reliability in Azure](../../reliability/availability-zones-overview.md)
0 commit comments