An IP you can transfer between servers
If you have a dedicated server with us, you may use the Failover IP feature for managing your projects, SSL certificates,etc.
The Failover IP may be moved from one server to another in a few seconds. An account with an Failover IP works without intervals and is the best solution in the event of hardware malfunction, overloaded applications or other infrastructure problems.
If you'd like to make use of all the advantages of having an Failover IP, your account configuration must be based on the Failover IP instead of the fixed IP address.
Moreover, if you move Failover IP between two servers, you will keep the configuration.
You need to make copies of your projects and configuration files between the servers. The configuration files for moving the Failover IP between two servers remain unchanged and all the services will work on the other server. You don't need to assign your projects to the new server's fixed IP.
Here are different examples of its use:
1) Change / Upgrade of the server
Your projects are on the dedicated server A (fixed IP A) and are configured to Failover Z.
You may order a new server if server A isn't sufficient to manage your projects. It's described as server B with fixed IP.
You need to make copies of your projects and configuration files from server A to B. Then...
... you can change the routing of Failover IP Z from server A to server B. Information about your projects, configuration files are assigned to your Failover IP on server B. It doesn't require any change in configuration (DNS, APACHE, SMTP, POP3, MySQL ...).
2) Functioning as the main server and the backup server
you have two servers A and B, the server A is your main server, server B is your backup server.
Your projects are configured on Failover IP Z, routed to server A. You can perform regular copies of your projects between the servers.
You can change the routing of Failover IP from server A to B when server A is down. All your services will work on server B. You will have time to repair your A server.
When the A server is repaired, you copy your data from server B to A. Then you change the routing of Failover IP for B to A. As a result all services work on the A server again.
This configuration has two advantages:
- you make a copy of data stored on A
- you use B server when A is down
3) Hosting of several projects
If you administer a larger number of websites, you may use 2 Failover IP addresses. Some of your websites will be assigned to Failover IP Y and the rest to Z.
When server A doesn't have enough power to manage sites on both Y and Z Failover IP, you may order a new server B and route Failover IP Z to the B server. Server A won't be administering the sites for Y Failover IP which will result in lowering the load and improving its performance.
Also discover: IP blocks