IP Fail-over

If you have a dedicated server with us, you may use the IP fail-over feature for managing your projects, SSL certificates,etc.
The IP fail-over may be moved from one server to another in a few seconds. An account with an IP fail-over works without intervals and is the best solution in case of hardware malfunction, overloaded applications or other infrastructure problems.

If you'd like to use all the advantages of having an IP fail-over, your account configuration must be based on the IP fail-over instead of the fixed IP address.
What's more, if you move IP fail-over 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 IP fail-over 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 fail-over 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 change the routing of IP fail-over Z from the server A to the server B. Information about your projects, configuration files that are assigned to your IP fail-over will work on server B. It doesn't require any change in configuration (DNS, APACHE, SMTP, POP3, MySQL ...).

2) Functioning of the main server and the backup server

you have two servers A and B, the A server is your main server, the B server is your backup server.
Your projects are configured on IP fail-over Z, routed to the A server. You make regular copies of your projects between the servers.

You change the routing of IP fail-over from server A to B when the A server is down. All your services work on the B server. You 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 IP fail-over 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 larger number of websites, you may use 2 IP fail-over addresses. Some of your websites will be assigned to IP fail-over Y and the rest to Z.

When server A doesn't have enough power to manage sites on both Y and Z IP fail-over, you may order a new server B and route IP fail-over Z to the B server. Server A won't be administering the sites for Y IP fail-over which will result in lowering the load and improving its performance.