Skip to content

Commit 0a76104

Browse files
Merge pull request #232676 from kabharati/atlantic0329
Update concepts-business-continuity.md
2 parents 2852716 + 0271c55 commit 0a76104

File tree

1 file changed

+12
-0
lines changed

1 file changed

+12
-0
lines changed

articles/postgresql/flexible-server/concepts-business-continuity.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -33,6 +33,18 @@ The table below illustrates the features that Flexible server offers.
3333
| **Geo redundant backup** | Flexible server backups are copied to a remote region. that helps with disaster recovery situation in the event of the primary server region is down. | This feature is currently enabled in selected regions. It takes a longer RTO and a higher RPO depending on the size of the data to restore and amount of recovery to perform. |
3434
| **Read Replica** | Cross Region read replicas can be deployed to protect your databases from region-level failures. Read replicas are updated asynchronously using PostgreSQL's physical replication technology, and may lag the primary. For more information, see [Concepts - Read Replicas](./concepts-read-replicas.md).| Supported in general purpose and memory optimized compute tiers. |
3535

36+
37+
The following table compares RTO and RPO in a **typical workload** scenario:
38+
39+
| **Capability** | **Burstable** | **General Purpose** | **Memory optimized** |
40+
| :------------: | :-------: | :-----------------: | :------------------: |
41+
| Point in Time Restore from backup | Any restore point within the retention period <br/> RTO - Varies <br/>RPO < 15 min| Any restore point within the retention period <br/> RTO - Varies <br/>RPO < 15 min | Any restore point within the retention period <br/> RTO - Varies <br/>RPO < 15 min |
42+
| Geo-restore from geo-replicated backups | RTO - Varies <br/>RPO < 1 h | RTO - Varies <br/>RPO < 1 h | RTO - Varies <br/>RPO < 1 h |
43+
| Read replicas | RTO - Minutes* <br/>RPO < 5 min* | RTO - Minutes* <br/>RPO < 5 min*| RTO - Minutes* <br/>RPO < 5 min*|
44+
45+
\* RTO and RPO **can be much higher** in some cases depending on various factors including latency between sites, the amount of data to be transmitted, and importantly primary database write workload.
46+
47+
3648
## Planned downtime events
3749

3850
Below are some planned maintenance scenarios. These events typically incur up to few minutes of downtime, and without data loss.

0 commit comments

Comments
 (0)