PostgreSQL Flexible server availability issue

Question

I want to create Azure Database for PostgreSQL Flexible server with High availability Zone redundant (99.99 SLA) but this option is unable to be selected it, only available Disabled (99.9% SLA) and Same zone (99.95% SLA)

east us region

@ShaktiSingh-MSFT can you help me?

Answer 1

Hi Youssef Yassa •,

Welcome to Microsoft Q&A forum.

As I understand, you want to create Azure Database for PostgreSQL Flexible server with High availability Zone redundant (99.99 SLA) but this option is unable to be selected it, only available Disabled (99.9% SLA) and Same zone (99.95% SLA) in East US.

Could you please check what Compute tier has been selected above HA option?

Try using General Purpose and see if the option appears for you.

Awaiting your reply.

Thanks

Answer 2

Hi Youssef Yassa •,

Zone redundancy:

• The zone-redundancy option is only available in regions that support availability zones.
• Zone-redundancy is not supported for:
  • Azure Database for PostgreSQL – Single Server SKU.
  • Burstable compute tier.
  • Regions with single-zone availability.

While creation of Flexible Server, select the checkbox for Enable high availability. That opens up an option to choose high availability mode. If the region doesn't support AZs, then only same-zone mode is enabled.

If high availability option is checked, the burstable tier isn't available to choose. You can choose either General purpose or Memory Optimized compute tiers. Then you can select compute size for your choice from the dropdown.

More details are here: https://learn.microsoft.com/en-us/azure/postgresql/flexible-server/how-to-manage-high-availability-portal

The Burstable tier is best suited for low-cost development and low concurrency workloads without continuous compute capacity.

However, Automatic backups happen in Flexible Sever, Azure Database for PostgreSQL flexible server automatically performs daily backups of your database files and continuously backs up transaction logs. Backups can be retained from 7 days up to 35 days. You're able to restore your database server to any point in time within your backup retention period. RTO is dependent on the size of the data to restore + the time to perform log recovery. It can be from few minutes up to 12 hours. For more details, see Concepts - Backup and Restore.

Read more about Business Continuity https://learn.microsoft.com/en-us/azure/postgresql/flexible-server/concepts-business-continuity

Hope this helps.

Let us know if you have more queries.

Thanks