An IP you can transfer between servers
When you have a dedicated server with OVH, you have the possibility to get failover IPs to host your projects, SSL certificates, etc. The failover IP can be switched from one server to another in a few seconds. Therefore, a failover IP allows your hosting services to operate without any interruption and helps you overcome hardware failure issues, system overruns and all kinds of infrastructure problems. In order to take full advantage of the failover IP's power, your hosting services must be configured with the failover IP (as opposed to the server's static IP).
So if you switch the failover IP from one server to another, you keep the entire configuration linked to that failover IP. You are responsible for copying your projects and configuration files from one server to the other. Since the configuration files are linked to the failover IP, and therefore the data and configurations remain the same, everything will keep working once you have switched the failover IP to the new server. You don't need to reconfigure all your projects with the static IP of your new server.
Server change / Server upgrade
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 IP Failover Z from server A to server B. Information about your projects, configuration files are assigned to your IP Failover on server B. It doesn't require any change in configuration (DNS, APACHE, SMTP, POP3, MySQL ...).
Working in a main server and a backup server
You have two servers: A and B. Server A is your main server, server B is your backup server.
Your projects are configured on IP Failover Z, routed to server A. You can perform regular copies of your projects between the servers.
You can change the routing of IP Failover 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 IP Failover 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 server B when A is down
Hosting several projects
If you administer a larger number of websites, you may use 2 IP Failover addresses. Some of your websites will be assigned to IP Failover Y and the rest to Z.
When server A doesn't have enough power to manage sites on both Y and Z IP Failover, you may order a new server B and route IP Failover Z to the B server. Server A won't be administering the sites for Y IP Failover which will result in lowering the load and improving its performance.