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.
- Set up a new GitHub Enterprise appliance on your desired platform. The replica appliance should mirror the primary appliance's CPU, RAM, and storage settings. We recommend that you install the replica appliance in an independent environment. The underlying hardware, software, and network components should be isolated from those of the primary appliance. If you are a using a cloud provider, use a separate region or zone. For more information, see "Provisioning and installation".
- In a browser, navigate to the new replica appliance's IP address and upload your GitHub Enterprise license.
- Set an admin password that matches the password on the primary appliance and continue.
- Click New Install to set up a new installation or migrate from another appliance.
- On the Settings page, add an SSH key to the list of authorized SSH keys. Use this key to:
- SSH to the replica appliance for initial setup.
- Monitor replication status.
- Perform manual failover (if necessary).
-
Connect to the replica appliance's IP address using SSH:
ssh -p 122 admin@REPLICA IP -
To generate a key pair for replication, use the
ghe-repl-setupcommand with the primary appliance's IP address and copy the public key that it returns:ghe-repl-setup PRIMARY IP To add the public key to the list of authorized keys on the primary appliance, browse to
https://<PRIMARY HOSTNAME>/setup/settingsand add the key you copied from the replica to the list.-
To verify the connection to the primary and enable replica mode for the new replica, run
ghe-repl-setupagain.ghe-repl-setup PRIMARY IP -
Use the
ghe-repl-startcommand to start replication of the datastores:ghe-repl-start -
Use the
ghe-repl-statuscommand to verify the status of each datastore's replication channel:ghe-repl-status
