---
title: "Replacing Servers"
canonical: "https://docs.infoblox.com/space/BloxOneInfrastructure/185106557/Replacing%20Servers"
format: markdown
---
If you need to replace an existing NIOS-X server with a new one (due to malfunctioning or misconfiguration on the old NIOS-X server), you can use the "replace" function to do so. You can replace NIOS-X virtual and NIOS-X physical servers. The “replace” function supports zero-touch provisioning through the Infoblox Portal.

> ⚠️ **Note**
> ⚠️ 
> ⚠️ To ensure that all the services moved from the old NIOS-X server operate properly on the new NIOS-X server, you must select a new server that can support all the services currently running on the existing server. Otherwise, certain services might not function properly on the new NIOS-X server. For example, if you replace an existing NIOS-X server running the Data Connector service with a new NIOS-X server that does not support the Data Connector service, the service will not be operational on the new server.

To replace an existing NIOS-X server (regardless of whether or not it is online), you first set up the new NIOS-X server and connect it to the Infoblox Portal through zero-touch provisioning. Ensure that the new NIOS-X server is in the Online state and that there are no active services enabled on the new server. The replace function will automatically remove the services from the old server and move them to the new server without the need for manual configuration. If the old server is not connected to the Infoblox Portal when the replace happens (e.g. it is powered off or has no Internet connectivity, etc), then it will continue to run the services locally until it has connected to Infoblox Portal and received instructions to remove all local services.

After replacing the data connector, the user must update the NIOS configuration with the new NIOS-X server IP. The new IP is the customer's NIOS-X server IP that replaced the old one.

The following table lists the respective states of the NIOS-X servers before, during, and after the replace operation.

| **Replace Operation** | **Old Server State** | **New Server State** |
| --- | --- | --- |
| Before operation | **Online** (with services running): This state is applicable only to NIOS-X servers that are already online.<br>**Offline**: This state is applicable to offline NIOS-X servers, such as misconfigured or corrupted NIOS-X servers. | **Online** (without services running) |
| During operation | **Pending** > **Awaiting Approval** | **Offline** |
| After operation | **Awaiting Approval**<br>**Note**: The NIOS-X server stays in the **Awaiting Approval** state and no action is required. | **Online** (with services running) |

To replace a server, complete the following:

1. <span style="color: #000000">From the Infoblox Portal, click </span>**Network > Services & Servers > Servers**<span style="color: #000000">. </span>
2. <span style="color: #000000">Select the the server you want to replace.</span>
3. <span style="color: #000000">Click </span><span style="color: #000000">**...**</span><span style="color: #000000"> next to the server</span><span style="color: #000000">** >**</span><span style="color: #000000"> </span><span style="color: #000000">**Replace**</span><span style="color: #000000">.</span>
4. <span style="color: #000000">In the replace server widget, select the new server from the </span><span style="color: #000000">**Replacement Server**</span><span style="color: #000000"> list, and then click </span><span style="color: #000000">**Save & Close**</span><span style="color: #000000">.</span>
5. <span style="color: #000000">A confirmation message is displayed. Click </span><span style="color: #000000">**Confirm **</span><span style="color: #000000">to replace the existing server with the new server, or click </span><span style="color: #000000">**Cancel **</span><span style="color: #000000">to cancel the operation.</span>

> ⚠️ **Notes**
> ⚠️ 
> ⚠️ - Once you confirm the operation, the old NIOS-X server goes into the Pending state and thereafter, goes into the Awaiting Approval state when (and if) it connects to the Infoblox Portal again. If it is functional, you can reuse the old NIOS-X server by Approving its membership and allowing it to come back online (though this is not a typical use case). It is typical to remove the old NIOS-X server from the network, delete the old VM, and delete the entry in the Infoblox Portal after the replace operation has completed.
> ⚠️ - It might take a few seconds for the replace operation to complete and all the services on the new server to go online.
> ⚠️ - When replacing NIOS-X servers, the services transition smoothly to the new server.  In addition, the Location and IP Space values are moved over (and removed from the old server configuration in the Infoblox Portal). However, no other host-level configuration such as Server name, Server description, tags, NTP settings, DNS local resolver, or IP interface settings will be copied over. If the new server had a different IP address at the time of the replace operation, it will continue to use the different IP address. It will not adopt the IP address of the old server. You will need to update the new server afterwards if you want it to have the same IP as the old server (either by updating the static IP address or possibly by updating DHCP server if using DHCP).
> ⚠️ - The Infoblox Portal supports flexible IP configurations during server replacement, allowing you to assign either the same or different IP addresses to participating hosts without any restrictions If you let the old server and the new server on the network at the same time with the same IP address, you will have a network conflict. IP address reuse is fully supported, enabling you to retain the same IP address during the replacement process if desired. If the old server is offline (and thus will not cause an IP conflict on the active network), it is typically easier to perform the replace operation if the new server has the same IP as the old server. This is so that the rest of the network does not have to be told about the IP address of the new server and also because the existing network security firewall policy will likely already permit all required traffic flows. However, every deployment is different and your requirements may vary<span style="color: #000000">. </span>

> ❌ <span style="color: #1d1c1d">After replacing a server that is part of a DHCP HA Group, if the new server has multiple IP addresses, check if the peer destination address is set to the desired one and update it if needed. For more information, see </span><span style="color: #1d1c1d">*[Creating HA Groups](https://infoblox-docs.atlassian.net/wiki/spaces/BloxOneDDI/pages/186467301)*</span><span style="color: #1d1c1d">.</span>

Currently the Replace operation is not supported for servers running the Anycast service. The GUI will permit the operation but it is not supported. If Anycast is enabled on the old server, you should disable Anycast on the old server (even if the sever is offline) before initiating the Replace operation. Failure to do so may result in unexpected behavior. After replacement, Anycast must be manually reconfigured on the new server if needed.