---
layout: docs
page_title: Redundancy Zones (Enterprise)
description: >-
Add non-voting servers to clusters to create redundancy zones for deployments. Learn how distributed ""hot standby"" servers improve resiliency and scaling by preserving quorum.
---

# Redundancy Zones

<EnterpriseAlert>
  This feature requires
  self-managed Consul Enterprise.
  Refer to the{' '}
  <a href="/docs/enterprise#consul-enterprise-feature-availability">enterprise feature matrix</a>
  {' '}for additional information.
</EnterpriseAlert>

Consul Enterprise redundancy zones provide
both scaling and resiliency 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) by also including recovery
capabilities.

For more information, complete the [Redundancy Zones](https://learn.hashicorp.com/tutorials/consul/autopilot-datacenter-operations#redundancy-zones) tutorial
and reference the [Consul Autopilot](/commands/operator/autopilot) documentation.