|
| 1 | +--- |
| 2 | +title: Dedicated Servers 3-AZ Reversibility Policy |
| 3 | +updated: 2025-06-24 |
| 4 | +--- |
| 5 | + |
| 6 | +## Objective |
| 7 | + |
| 8 | +This document is the reversibility policy for the Dedicated Servers 3AZ product range. |
| 9 | + |
| 10 | +This policy aims at implementing the global reversibility principles and requirements of SWIPO IaaS Code of Conduct for Cloud Providers. |
| 11 | + |
| 12 | +## Features map |
| 13 | + |
| 14 | +Dedicated Servers features are divided into three categories: |
| 15 | + |
| 16 | +1. **Core features** for which we guarantee migration capacity. |
| 17 | +1. **OVHcloud implementations** that require adaptation to a new migration environment. |
| 18 | +1. **Specific features** that cannot be guaranteed for migration as they are related to the OVHcloud environment or involve custom developments. |
| 19 | + |
| 20 | +### Core features <a name="core-features"></a> |
| 21 | + |
| 22 | +|Feature|Description|Available formats|Migration model|Available documentation| |
| 23 | +|---|-----|---|-----|-----| |
| 24 | +|Supplying dedicated servers|Supplying different ranges of high-performance dedicated servers|N/A|**Inbound migration**: Order a dedicated server in the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.co.uk/&ovhSubsidiary=GB), backup and migrate data, re-install software (or use automated installation).<br><br>**Outbound migration**: Order dedicated servers, backup and migrate data, re-install software|[Getting started with a dedicated server](/pages/bare_metal_cloud/dedicated_servers/getting-started-with-dedicated-server)| |
| 25 | +|Backup storage|Backup storage delivered by default with every dedicated server|NFS/CIFS/FTP|**Inbound migration**: Migrate data on your dedicated servers and activate backup storage on those servers through the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.co.uk/&ovhSubsidiary=GB).<br><br>**Outbound migration**: enable access from outside your account through OVHcloud API, then migrate data using standard file transfer protocols, such as FTP.|[Using backup storage on a dedicated server](/pages/bare_metal_cloud/dedicated_servers/services_backup_storage)| |
| 26 | +|Operating systems and software installed on dedicated server|Automatically install operating systems, databases, administration interfaces and virtualization software on a new dedicated server.<br>See [here](https://www.ovhcloud.com/en-gb/bare-metal/os/) the complete list.|For customized images used with "bring your own image": <br>- Boot type: **uefi** or **legacy**<br>- Partition type: **MBR** or **GPT**<br>- Image format: **qcow2** or **raw**|**Inbound migration**: Order dedicated servers and choose operating systems/software to install on the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.co.uk/&ovhSubsidiary=GB). Alternatively, use the"bring your own image" feature to install customized images.<br><br>**Outbound migration**: Export your image and install on another dedicated server.|[Installing or reinstalling your dedicated server](/pages/bare_metal_cloud/dedicated_servers/getting-started-with-dedicated-server#installing-or-reinstalling-your-dedicated-server)<br><br>[How to use the Bring Your Own Image feature](/pages/bare_metal_cloud/dedicated_servers/bring-your-own-image)| |
| 27 | +| Bring Your Own IP | Allows the customer to import their own public IPv4 address ranges (from /24 to /19) into the OVHcloud infrastructure.| Public IP adresses registred in RIR | **Inbound migration**: --- <br> **Inbound migration**:-----| [How to use the Bring Your Own IP feature](/pages/network/bring_your_own_ip/bring-your-own-IP) | |
| 28 | + |
| 29 | +### OVHcloud implementation <a name="ovhcloud-implementation"></a> |
| 30 | + |
| 31 | +|Feature|Description|Available formats|Migration model|Available documentation| |
| 32 | +|---|-----|---|-----|-----| |
| 33 | +|Floating IPs|Additional IP that can be switched from one service to another in the same datacenter.|IPv4, IPv6|**Inbound migration**: Plan the network architecture, configure the Floating IPs in the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.co.uk/&ovhSubsidiary=GB) or through OVHcloud API.<br><br>**Outbound migration**: Record the configured setup in the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.co.uk/&ovhSubsidiary=GB) and configure a similar setup at another provider.|[Moving an Additional IP](/pages/bare_metal_cloud/dedicated_servers/move-failover-ip)<br><br>[Assigning a virtual MAC to an Additional IP](/pages/bare_metal_cloud/dedicated_servers/network_virtual_mac)| |
| 34 | +|vRack|vRack, or Virtual rack, is a private VLAN technology that enables connection between OVHcloud services.|N/A|**Inbound migration**: Plan the network architecture, Add your servers to the vRack, Configure network interfaces.<br><br>**Outbound migration**: Record the network architecture and reproduce it with VLAN.|[Configuring the vRack on your dedicated servers](/pages/bare_metal_cloud/dedicated_servers/vrack_configuring_on_dedicated_server)| |
| 35 | + |
| 36 | +### Specific functionalities <a name="specific-functionalities"></a> |
| 37 | + |
| 38 | +|Feature|Description|Available formats|Migration model|Available documentation| |
| 39 | +|---|-----|---|-----|-----| |
| 40 | +|Load Balancing|Load Balancers are network devices that distribute requests across services and datacenters to ensure that there is no overload.|N/A|**Inbound migration**: Purchase and activation through [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.co.uk/&ovhSubsidiary=GB).<br><br>**Outbound migration**: Order and set up a load balancer with the new provider.|**Inbound migration**: [OVHcloud Load Balancers](https://www.ovh.co.uk/solutions/load-balancer/)<br><br>**Outbound migration**: N/A| |
| 41 | +|Anti-DDoS|The anti-DDoS is a set of equipment and means put in place to absorb distributed denial of service attacks. It includes an analysis of traffic, the "aspiration" towards a specialized network, and mitigation, ensured by VAC technology developed by OVHcloud.|N/A|**Inbound migration**: The anti-DDoS is a component of our infrastructure, enabled by default. No action is required.<br><br>**Outbound migration**: Order and configure an anti-DDoS with the new provider.|**Inbound migration**: [OVHcloud anti-DDoS protection](https://www.ovh.co.uk/anti-ddos/) and [Anti-DDoS Technology](https://www.ovh.co.uk/anti-ddos/anti-ddos-technology.xml)<br><br>**Outbound migration**: N/A| |
| 42 | + |
| 43 | +### Architecture listing |
| 44 | + |
| 45 | +All components of the OVHcloud Dedicated Server product are accessible through the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.co.uk/&ovhSubsidiary=GB). this allows to visualize and manage the dedicated servers, installed images, network configuration ... as well as the features that are attached to these components. |
| 46 | + |
| 47 | +### Partner services |
| 48 | + |
| 49 | +OVHcloud Partners are listed with the "Cloud Migration" keyword in the dedicated [directory](https://partner.ovhcloud.com/en-gb/directory/). |
| 50 | + |
| 51 | +### Cost and fees |
| 52 | + |
| 53 | +No additional billing is planned from OVHcloud for the migration features listed here. |
| 54 | + |
| 55 | +### Retention of data after contract termination |
| 56 | + |
| 57 | +If a customer explicitly terminates his use of a given host, the data is erased 24 hours thereafter. In case of contract termination without explicit release of hosts, the data is retained 7 days and then deleted permanently. |
0 commit comments