2017-05-05 05:24:04 +00:00
|
|
|
---
|
|
|
|
|
layout: "docs"
|
|
|
|
|
page_title: "Consul Enterprise Redundancy Zones"
|
|
|
|
|
sidebar_current: "docs-enterprise-redundancy"
|
|
|
|
|
description: |-
|
|
|
|
|
Consul Enterprise redundancy zones enable hot standby servers on a per availability zone basis.
|
|
|
|
|
---
|
|
|
|
|
|
2020-03-24 20:06:20 +00:00
|
|
|
# Redundancy Zones
|
2017-05-05 05:24:04 +00:00
|
|
|
|
2020-03-24 20:06:20 +00:00
|
|
|
[Consul Enterprise](https://www.hashicorp.com/consul.html) redundancy zones provide
|
|
|
|
|
both scaling and resiliancy benefits by enabling the deployment of non-voting
|
|
|
|
|
servers alongside voting servers on a per availability zone basis.
|
|
|
|
|
|
|
|
|
|
When using redundancy zones, if an operator chooses to deploy Consul across 3 availability zones, they
|
|
|
|
|
could have 2 (or more) servers (1 voting/1 non-voting) in each zone. In the event that a voting
|
|
|
|
|
member in an availability zone fails, the redundancy zone configuration would automatically
|
|
|
|
|
promote the non-voting member to a voting member. In the event that an entire availability
|
|
|
|
|
zone was lost, a non-voting member in one of the existing availability zones would promote
|
|
|
|
|
to a voting member, keeping server quorum. This capability functions as a "hot standby"
|
|
|
|
|
for server nodes while also providing (and expanding) the capabilities of
|
|
|
|
|
[enhanced read scalability](/docs/enterprise/read-scale/index.html) by also including recovery
|
|
|
|
|
capabilities.
|
|
|
|
|
|
|
|
|
|
For more information, review the HashiCorp Learn guide on
|
|
|
|
|
[Redundancy Zones](https://learn.hashicorp.com/consul/day-2-operations/autopilot#redundancy-zones),
|
|
|
|
|
as well as the documentation for [Consul Autopilot](https://www.consul.io/docs/commands/operator/autopilot.html).
|
