> ## Documentation Index
> Fetch the complete documentation index at: https://docs.canton.network/llms.txt
> Use this file to discover all available pages before exploring further.

# High Availability

> Configure high availability for Canton participant and synchronizer nodes

# High Availability

High availability (HA) for Canton nodes means running replicated instances that share a database so a passive replica can take over when the active instance fails. Use these howtos when you need resilient participant or synchronizer infrastructure.

<Note>
  Party multi-hosting improves resilience for a *party*, not for a node process. For node-level failover, use the replicated setups below.
</Note>

## Guides

* [Participant high availability](/global-synchronizer/production-operations/high-availability-participant) — active/passive participant replicas, fail-over, and load balancer health checks
* [Synchronizer high availability](/global-synchronizer/production-operations/high-availability-synchronizer) — mediator replicas and horizontally scaled database sequencers

## Requirements

* Shared storage between replicas (PostgreSQL; Oracle where noted on the participant page)
* Replication / sequencer HA settings as described in each howto

## Related references

* Console: [`replication.set_passive`](/global-synchronizer/reference/canton-console-commands#replication.set_passive) and [`synchronizers.connect_multi`](/global-synchronizer/reference/canton-console-commands#synchronizers.connect_multi)
* [Observability configuration](/global-synchronizer/reference/observability-configuration) for health endpoints used by load balancers