Skip to content

Commit 0fccf95

Browse files
lronpawhubwriter
andauthored
Add to Changing GHES Hostname doc with explicit mentions for IP address and HA (#55908)
Co-authored-by: hubwriter <hubwriter@github.com>
1 parent b726ba6 commit 0fccf95

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

content/admin/configuring-settings/configuring-network-settings/changing-the-hostname-for-your-instance.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,8 @@ If you need to use a new hostname for {% data variables.location.product_locatio
1919

2020
Migration to a new instance requires downtime. The amount of downtime required depends on how much data you need to back up, as well as the speed of the network connection between the backup host and the instances.
2121

22+
The new instance cannot directly replace an existing instance in a high availability configuration. Ensuring the new instance is configured with a different IP address to the instance with the old hostname is strongly recommended, and can simplify roll back. In high availability environments, once the restore is complete and the state of the new instance has been validated, you can then proceed with using a fresh appliance, or reconfiguring an existing replica. See [AUTOTITLE](/admin/monitoring-and-managing-your-instance/configuring-high-availability/creating-a-high-availability-replica).
23+
2224
In this article, the term "source instance" refers to the instance with the old hostname, and "destination instance" refers to the instance with the new hostname.
2325

2426
{% data reusables.enterprise_installation.changing-hostname-not-supported %}

0 commit comments

Comments
 (0)