2017-05-05 05:24:04 +00:00
---
2020-04-07 18:55:19 +00:00
layout: docs
page_title: Consul Enterprise Redundancy Zones
2020-04-13 18:40:26 +00:00
sidebar_title: Redundancy Zones
2020-04-07 18:55:19 +00:00
description: >-
Consul Enterprise redundancy zones enable hot standby servers on a per
availability zone basis.
2017-05-05 05:24:04 +00:00
---
2020-03-24 20:06:20 +00:00
# Redundancy Zones
2017-05-05 05:24:04 +00:00
2020-04-23 22:13:18 +00:00
<EnterpriseAlert>
This feature requires <a href="https://www.hashicorp.com/products/consul/">Consul Enterprise</a> with the Global Visibility, Routing, and Scale module.
</EnterpriseAlert>
Consul Enterprise redundancy zones provide
both scaling and resiliency benefits by enabling the deployment of non-voting
2020-04-06 20:27:35 +00:00
servers alongside voting servers on a per availability zone basis.
2020-03-24 20:06:20 +00:00
2020-04-06 20:27:35 +00:00
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
2020-04-09 23:20:00 +00:00
[enhanced read scalability](/docs/enterprise/read-scale) by also including recovery
2020-04-06 20:27:35 +00:00
capabilities.
2020-03-24 20:06:20 +00:00
2020-04-06 20:27:35 +00:00
For more information, review the HashiCorp Learn guide on
[Redundancy Zones](https://learn.hashicorp.com/consul/day-2-operations/autopilot#redundancy-zones),
2020-04-09 23:46:54 +00:00
as well as the documentation for [Consul Autopilot](/docs/commands/operator/autopilot).
