Frecuentemente publicamos actualizaciones de nuestra documentación. Es posible que la traducción de esta página esté en curso. Para conocer la información más actual, visita la documentación en inglés. Si existe un problema con las traducciones en esta página, por favor infórmanos.

Initiating a failover to your replica cluster

If your Servidor de GitHub Enterprise cluster fails, you can fail over to the passive replica .

En este artículo

About failover to your replica cluster

In the event of a failure at your primary datacenter, you can fail over to the replica nodes in the secondary datacenter if you configure a passive replica node for each node in your active cluster.

The time required to fail over depends on how long it takes to manually promote the replica cluster and redirect traffic.

Promoting a replica cluster does not automatically set up replication for the existing cluster. After promoting a replica cluster, you can reconfigure replication from the new active cluster. For more information, see "Configuring high availability for a cluster."


To fail over to passive replica nodes, you must have configured high availability for your cluster. For more information, see "Configuring high availability for a cluster."

Initiating a failover to your replica cluster

  1. SSH into any passive node in the secondary datacenter for your cluster. Para obtener más información, consulta "Acceder al shell administrativo (SSH)."

  2. Initialize the failover to the secondary cluster and configure it to act as the active nodes.

  3. After the configuration run finishes, Servidor de GitHub Enterprise displays the following message.

    Finished cluster configuration
  4. Update the DNS record to point to the IP address of the load balancer for your passive cluster. El tráfico es direccionado a la réplica después de que transcurra el período TTL.

After Servidor de GitHub Enterprise returns you to the prompt and your DNS updates have propagated, you've finished failing over. Users can access Servidor de GitHub Enterprise using the usual hostname for your cluster.

¿Te ayudó este documento?

Privacy policy

Help us make these docs great!

All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.

Make a contribution

O, learn how to contribute.