이 버전의 GitHub Enterprise는 다음 날짜에 중단되었습니다. 2025-04-03. 중요한 보안 문제에 대해서도 패치 릴리스가 이루어지지 않습니다. 더 뛰어난 성능, 향상된 보안, 새로운 기능을 위해 최신 버전의 GitHub Enterprise Server로 업그레이드합니다. 업그레이드에 대한 도움말은 GitHub Enterprise 지원에 문의하세요.

Changing your platform

How to change the platform that runs GitHub Enterprise Server 인스턴스

이 문서의 내용

In some cases, you may need to change the platform on which 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 스테이징 인스턴스 설정.

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 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 GitHub Enterprise Server 인스턴스 설정.
  2. Configure your new GitHub Enterprise Server instance as a replica. See 고가용성 복제본 만들기.
  3. Failover to your replica. See 복제본 어플라이언스로 장애 조치(failover) 시작.

Moving platforms using backup and restore

  1. Setup backups for your existing GitHub Enterprise Server instance. See 인스턴스에서 백업 구성.

  2. Set up a new GitHub Enterprise Server instance on your chosen platform. See GitHub Enterprise Server 인스턴스 설정.

  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 GitHub Actions를 사용할 수 있는 GitHub Enterprise 서버 백업 및 복원

  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