Synchronous Streaming Replication

A second database node maintains a continuously-synchronized copy of your tenant database. Writes are acknowledged on both nodes before completing, so the standby is always current.

Automatic Failover

On primary-node failure, the standby is promoted automatically. Connections fail over without manual intervention; in-flight transactions retry transparently.

Independent Maintenance

Patching and minor-version upgrades happen on the standby first. The primary follows once the standby is healthy, with zero downtime to your users.

Strict Uptime SLA

Choose HA when your business commitments require named-uptime targets — typically 99.95% or better measured monthly.

Regulated Industries

Some regulators require demonstrable failover capability for systems-of-record. The HA add-on meets that bar.

Mission-Critical Operations

For tenants whose field operations cannot pause for a database restart — dispatch fleets, 24/7 logistics, time-sensitive compliance.

Not a Geographic DR Solution

HA covers single-node failure within the managed-database cluster. It is not a multi-region disaster-recovery solution. For multi-region resilience, contact us for an enterprise discussion.

Not a Backup Replacement

A standby node replicates corruption as faithfully as it replicates writes. The Daily Backups capability is your protection against accidental data loss; HA is your protection against hardware failure.