Skip to content

Commit

Permalink
Merge pull request #1978 from OctopusDeploy/tk/high-availability-lice…
Browse files Browse the repository at this point in the history
…nsing-update

Update high availability licensing information
  • Loading branch information
steve-fenton-octopus authored Aug 24, 2023
2 parents 7923931 + 462dc3b commit 29fd0e5
Showing 1 changed file with 4 additions and 7 deletions.
11 changes: 4 additions & 7 deletions src/pages/docs/administration/high-availability/index.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
layout: src/layouts/Default.astro
pubDate: 2023-01-01
modDate: 2023-01-01
modDate: 2023-08-24
title: High Availability
description: Octopus High Availability (HA) enables you to run multiple Octopus Server nodes, distributing load and tasks between them.
hideInThisSection: true
Expand Down Expand Up @@ -29,13 +29,10 @@ An Octopus High Availability configuration requires four main components:

Each Octopus Deploy SQL Server database is a unique **Instance**. Nodes are the Octopus Server service that connects to the database. High Availability occurs when two or more nodes connect to the same Octopus Deploy database. An HA Cluster refers to all components, the load balancer, nodes, database, and shared storage.

For self-hosted customers, High Availability is available to the following licenses type:
For self-hosted customers, High Availability is available for the following license types:

- High Avalability (discontinued license type): limited to 2, 3, or 4 nodes.
- Data Center (discontinued license type): unlimited nodes
- Server: unlimited nodes

All other license types, such as Standard, Enterprise, Team, and Professional, are limited to a single node and cannot be used for High Availablity.
- Professional: limited to 2 nodes
- Enterprise: unlimited nodes

The node limit is included in the license key in the NodeLimit node.

Expand Down

0 comments on commit 29fd0e5

Please sign in to comment.