GitHub Enterprise supports a high availability mode of operation designed to minimize service disruption in the event of hardware failure or major network outage affecting the primary appliance.

About High Availability configuration

In a High Availability configuration, a fully redundant secondary GitHub Enterprise appliance is kept in sync with the primary appliance through replication of all major datastores.

Creating a High Availability replica

In an active/passive configuration, the replica appliance is a redundant copy of the primary appliance. If the primary appliance fails, high availability mode allows the replica to act as the primary appliance, allowing minimal service disruption.

Initiating a failover to your replica appliance

You can failover to a GitHub Enterprise replica appliance using the command-line for maintenance and testing, or if the primary appliance fails.

Recovering a High Availability configuration

After failing over to a GitHub Enterprise appliance, you should regain redundancy as soon as possible rather than rely on a single appliance.

Removing a High Availability replica

You can stop replication to a GitHub Enterprise replica temporarily, or permanently remove replication.

About Geo-replication

GitHub Enterprise Geo-replication uses multiple active replicas to fulfill requests from geographically distributed data centers.