Changing your platform

How to change the platform that runs tu instancia de GitHub Enterprise Server

En este artículo

In some cases, you may need to change the platform on which tu instancia de GitHub Enterprise Server runs, such as moving from VMware to Azure.

Recommendations

You should carefully plan any out migration procedures and consider first testing on a staging environment. For more information, see Configurar una instancia de preparación.

Moving platforms using a replica will require the least amount of time for the migration process but will require you to make changes to your live environment in order to setup the replication.

Moving via backup and restore will not require any changes to your live environment, however the migration will take a significant amount of time. The specific amount of time to complete the migration will vary based the performance of your backup host, and the network speeds between your backup host and the new instance. Maintenance mode should also be enabled throughout the process otherwise users may be able to make changes which will not be reflected on your new instance.

Warning

You should not use utilities which convert tu instancia de GitHub Enterprise Server from one platform to another. Doing so could cause unintended side effects such as system instability.

Move platforms using a HA replica

  1. Set up a new GitHub Enterprise Server instance on your chosen platform. See Configurar una instancia del servidor de GitHub Enterprise.
  2. Configure your new GitHub Enterprise Server instance as a replica. See Crear una réplica de alta disponibilidad.
  3. Failover to your replica. See Iniciar una tolerancia de fallos a tu aparato de réplica.

Moving platforms using backup and restore

  1. Setup backups for your existing GitHub Enterprise Server instance. See Configuración de copias de seguridad en la instancia.

  2. Set up a new GitHub Enterprise Server instance on your chosen platform. See Configurar una instancia del servidor de GitHub Enterprise.

  3. Communicate the upcoming downtime to your users and enable maintenance mode. For more information, see the following articles.

  4. Create a new backup of your existing GitHub Enterprise Server instance.

  5. Restore the backup to your new GitHub Enterprise Server instance. If you are using GitHub Actions, see Respaldar y restablecer GitHub Enterprise Server con GitHub Actions habilitadas

  6. Update the DNS to point to the address of your new GitHub Enterprise Server instance.

  7. Disable maintenance mode and let users know they can continue normal operations.

Further reading