Skip to content

Commit ff8403a

Browse files
Merge pull request #215095 from AwdotiaRomanowna/main
Update overview.md
2 parents bb48808 + e816244 commit ff8403a

File tree

1 file changed

+1
-11
lines changed

1 file changed

+1
-11
lines changed

articles/postgresql/flexible-server/overview.md

Lines changed: 1 addition & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -36,20 +36,10 @@ Flexible servers are best suited for
3636
- Zone redundant high availability
3737
- Managed maintenance windows
3838

39-
## High availability
39+
## Architecture and high availability
4040

4141
The flexible server deployment model is designed to support high availability within a single availability zone and across multiple availability zones. The architecture separates compute and storage. The database engine runs on a container inside a Linux virtual machine, while data files reside on Azure storage. The storage maintains three locally redundant synchronous copies of the database files ensuring data durability.
4242

43-
During planned or unplanned failover events, if the server goes down, the service maintains high availability of the servers using following automated procedure:
44-
45-
1. A new compute Linux VM is provisioned.
46-
2. The storage with data files is mapped to the new Virtual Machine
47-
3. PostgreSQL database engine is brought online on the new Virtual Machine.
48-
49-
Picture below shows transition for VM and storage failure.
50-
51-
:::image type="content" source="./media/overview/overview-azure-postgres-flex-virtualmachine.png" alt-text="Flexible server - VM and storage failures":::
52-
5343
If zone redundant high availability is configured, the service provisions and maintains a warm standby server across availability zone within the same Azure region. The data changes on the source server are synchronously replicated to the standby server to ensure zero data loss. With zone redundant high availability, once the planned or unplanned failover event is triggered, the standby server comes online immediately and is available to process incoming transactions. This allows the service resiliency from availability zone failure within an Azure region that supports multiple availability zones as shown in the picture below.
5444

5545
:::image type="content" source="./media/business-continuity/concepts-zone-redundant-high-availability-architecture.png" alt-text="Zone redundant high availability":::

0 commit comments

Comments
 (0)