diff --git a/website/source/docs/enterprise/backups/index.html.md b/website/source/docs/enterprise/backups/index.html.md index 7aa0561ab9..231468a113 100644 --- a/website/source/docs/enterprise/backups/index.html.md +++ b/website/source/docs/enterprise/backups/index.html.md @@ -10,10 +10,10 @@ description: |- Consul's core snapshot functionality allows operators to save and restore the state of the Consul servers for disaster recovery. Snapshots are atomic and -point-in-time, and include key/value entries, service catalog, prepared +point-in-time, and include key/value entries, service catalog, prepared queries, sessions, and ACLs. [Consul Enterprise](https://www.hashicorp.com/consul.html) provides a [highly -available service](https://www.consul.io/docs/commands/snapshot/agent.html) that +available service](/docs/commands/snapshot/agent.html) that integrates with the snapshot API to automatically manage taking snapshots, -perform rotation and send backup files offsite to Amazon S3. +perform rotation and send backup files offsite to Amazon S3. diff --git a/website/source/docs/enterprise/federation/index.html.md b/website/source/docs/enterprise/federation/index.html.md index 3a51af6815..52ccef6ee7 100644 --- a/website/source/docs/enterprise/federation/index.html.md +++ b/website/source/docs/enterprise/federation/index.html.md @@ -17,7 +17,7 @@ desirable to have topologies like hub-and-spoke with central management datacenters and "spoke" datacenters that can't interact with each other. [Consul Enterprise](https://www.hashicorp.com/consul.html) offers a [network -area mechanism](https://www.consul.io/docs/guides/areas.html) that allows operators to +area mechanism](/docs/guides/areas.html) that allows operators to federate Consul datacenters together on a pairwise basis, enabling partially-connected network topologies. Once a link is created, Consul agents can make queries to the remote datacenter in service of both API and DNS diff --git a/website/source/docs/enterprise/read-scale/index.html.md b/website/source/docs/enterprise/read-scale/index.html.md index a6b565f00b..2f4b033281 100644 --- a/website/source/docs/enterprise/read-scale/index.html.md +++ b/website/source/docs/enterprise/read-scale/index.html.md @@ -12,5 +12,5 @@ In [Consul Enterprise](https://www.hashicorp.com/consul.html), servers can be explicitly marked as non-voters. Non-voters will receive the replication stream but will not take part in quorum (required by the leader before log entries can be committed). Adding explicit non-voters will [scale -reads](https://www.consul.io/docs/guides/autopilot.html#server-read-scaling) +reads](/docs/guides/autopilot.html#server-read-scaling) without impacting write latency. diff --git a/website/source/docs/enterprise/redundancy/index.html.md b/website/source/docs/enterprise/redundancy/index.html.md index 9a473e4733..a60c538e91 100644 --- a/website/source/docs/enterprise/redundancy/index.html.md +++ b/website/source/docs/enterprise/redundancy/index.html.md @@ -9,7 +9,7 @@ description: |- # Consul Enterprise Redundancy Zones [Consul Enterprise](https://www.hashicorp.com/consul.html) [redundancy -zones](https://www.consul.io/docs/guides/autopilot.html#redundancy-zones) make +zones](/docs/guides/autopilot.html#redundancy-zones) make it possible to have more servers than availability zones. For example, in an environment with three availability zones it's now possible to run one voter and one non-voter in each availability zone, for a total of six servers. If an diff --git a/website/source/docs/enterprise/upgrades/index.html.md b/website/source/docs/enterprise/upgrades/index.html.md index 99926b435d..f9d260614d 100644 --- a/website/source/docs/enterprise/upgrades/index.html.md +++ b/website/source/docs/enterprise/upgrades/index.html.md @@ -9,7 +9,7 @@ description: |- # Consul Enterprise Automated Upgrades [Consul Enterprise](https://www.hashicorp.com/consul.html) supports an [upgrade -pattern](https://www.consul.io/docs/guides/autopilot.html#upgrade-migrations) +pattern](/docs/guides/autopilot.html#upgrade-migrations) that allows operators to deploy a complete cluster of new servers and then just wait for the upgrade to complete. As the new servers join the cluster, server introduction logic checks the version of each Consul server. If the version is