-
Virtual endpoints: Regardless of the server role swaps, the writer endpoint always connects to the current primary server, and the reader endpoint points to the current replica. Virtual endpoints ensure you don't need to change connection strings in your applications, keeping things straightforward and hassle-free.
- Promote to primary server: This feature enables a quick and seamless transition between your primary database and its replica, minimizing downtime and maintaining continuity during unexpected regional disruptions.
To locate this feature, simply navigate to the replication blade in the Azure portal. Here, you can manage these settings and familiarize yourself with the seamless disaster recovery options available.
Screenshot of replication blade in the Azure portal.
Disaster recovery simplified
Diagram of promote to primary server flow.
What about the Previous Promote Feature?
Promote to independent server and remove from replication: This action, previously known as the 'promote' option, is renamed to better distinguish it from the 'Promote to primary server' capability, which allows switching between primary and replica server roles within a replication setup. This action in Flexible Server is similar to the 'stop replication' feature in Azure Database for PostgreSQL Single Server, which is set to retire.
Diagram of promote to independent server flow.
Data Integrity During Promotion
- Planned: Ensures full data synchronization before accepting client connections, safeguarding against data loss.
- Forced: Suitable for urgent recovery needs, such as during a regional outage, prioritizing quick restoration without data synchronization.
Changes from public preview to general availability
- Server symmetry checks for forced promotions: We introduced new checks for the 'forced' promote option when promoting a replica to a primary server. These checks ensure that the primary and replica servers meet server symmetry requirements. This improvement help maintain the integrity of the replication and avoids the need to recreate the old primary when failing back. If a replica doesn't meet these symmetry requirements, the promotion attempt results in an error. However, in scenarios where a region is down, the replica is promoted without any checks to ensure swift recovery.
- Private link support: We expanded our networking options to include Private link support. This addition complements the existing networking capabilities, which include public access and private access via virtual network integration. Now, users can choose from three networking options to best suit their security and connectivity needs.
Learn more
Further information about the new read replica features in Azure Database for PostgreSQL - Flexible Server is available through the links below: