|
1 | 1 | ---
|
2 | 2 | title: Web Hosting Reversibility Policy (DE)
|
3 |
| -updated: 2021-05-05 |
| 3 | +updated: 2025-08-25 |
4 | 4 | ---
|
5 | 5 |
|
6 | 6 | ## Objective
|
7 | 7 |
|
8 |
| -This document is the reversibility policy for the **Web Hosting** product for the [domain name](/links/web/domains) activity. |
| 8 | +This document describes the reversibility policy for the Managed Web Hosting product covering the OVHcloud Web Hosting offer. |
9 | 9 |
|
10 |
| -This policy aims at implementing the global reversibility principles and requirements of [SWIPO IaaS Code of Conduct for Cloud Providers](https://swipo.eu/download-section/copyrighted-downloads/). |
| 10 | +This policy aims to implement the general reversibility principles and our compliance with the SWIPO IAAS Code of Conduct for cloud providers. |
11 | 11 |
|
12 |
| -## Features map |
13 | 12 |
|
14 |
| -**Web Hosting** features are divided into three categories: |
| 13 | +## List of features |
15 | 14 |
|
16 |
| -- The [core features](#core-features) for which we guarantee the ability to migrate |
17 |
| -- The [OVHcloud implementation](#ovhcloud-implementation), whose migration will require adaptations to a new environment. |
18 |
| -- [Specific functionalities](#specific-functionalities), whose migration as such is impossible to guarantee as they are tied to OVHcloud environment or specific developments. |
| 15 | +Features of the product line fall into three categories: |
19 | 16 |
|
20 |
| -### Core features |
| 17 | +1. **Core features** for which we guarantee migration capacity. |
| 18 | +2. **OVHcloud implementations** that require adaptation to a new migration environment. |
| 19 | +3. **Specific features** that cannot be guaranteed for migration as they are related to the OVHcloud environment or involve custom developments. |
21 | 20 |
|
22 |
| -|Feature|Description|Available formats|Migration model|Available documentation| |
23 |
| -|----|-----|---|-----|-----| |
24 |
| -|Register and manage Domain names|Reservation and registration of domain names with domain name registrars.<br><br>DNS setting of domain names.|N/A|**Inbound migration**: Transfer request to original registrar and then manage via [OVHcloud Control Panel](/links/manager)<br><br>**Outbound migration**: Fully managed transfer request in [OVHcloud Control Panel](/links/manager).|**Inbound migration**: [Transferring a domain name to OVHcloud](/pages/web_cloud/domains/transfer_incoming_generic_domain)<br><br>[Transferring a .co.uk domain name to OVHcloud](/pages/web_cloud/domains/transfer_incoming_couk)<br><br>**Outbound migration**: [Transferring a domain name to another registrar](/pages/web_cloud/domains/transfer_outgoing_domain)<br><br>[Transferring a .co.uk domain name to another registrar](/pages/web_cloud/domains/transfer_outgoing_couk)| |
25 |
| -|Web hosting - Providing HTTP Servers|Provision of a web front-end server and code execution environment|**PHP**: 7.3 / 7.2 / 7.1 / 7.0 / 5.6<br><br>**Node.js**: 8 / 10 / 11|**Inbound migration**: Order a new OVHcloud hosting.<br><br>**Outbound migration**: Order a new hosting from the new provider. Replicate the runtime environment configuration from the Control Panel or .ovhconfig file.|**Inbound migration**:<br>[Getting started with a web hosting - Define your project](/pages/web_cloud/web_hosting/hosting_first_steps_with_web_hosting#step-1-define-your-project)<br><br>[Getting started with Cloud Web - Define your project](/pages/web_cloud/web_hosting/getting_started_cloud_web#step-1-define-your-project)<br><br>[Configuring the .ovhconfig file of your web hosting plan](/pages/web_cloud/web_hosting/configure_your_web_hosting)<br><br>**Outbound migration**: [Configuring the .ovhconfig file of your web hosting plan](/pages/web_cloud/web_hosting/configure_your_web_hosting)<br><br>[Configuring PHP from your customer account](/pages/web_cloud/web_hosting/configure_your_web_hosting)<br><br>Note: these documents allow you to retrieve relevant information about the .ovhconfig file and the PHP version.| |
26 |
| -|Web hosting - Providing file servers.|Provision of a file server to host the component files of the website (pages, scripts, resources...)|**Every format** - clients may upload any file on the server.|**Inbound migration**: FTP connection to the file server and import.<br><br>**Outbound migration**: FTP connection and file recovery.|**Inbound migration**: [Migrating your website to OVHcloud](/pages/web_cloud/web_hosting/hosting_migrating_to_ovh)<br><br>**Outbound migration**: [Export a website - retrieve files from your FTP storage space](/pages/web_cloud/web_hosting/exporter-son-site-web#step-1-retrieve-files-from-your-ftp-storage-space)| |
27 |
| -|Web hosting - providing databases|Provision of databases that can be connected to the website|**Shared SQL offers**:<br><br>**MySQL 5.6**<br><br>**Private SQL offers**:<br><br>**MySQL** 5.6 / 5.7<br><br>**MariaDB** 10.1<br><br>**PostgreSQL** 9.4 / 9.5 / 9.6 / 10|**Inbound migration**: Create a new database, then import the data by one of the available methods (backup restore, phpMyAdmin interface, script, SSH connection)<br><br>**Outbound migration**: Export data by one of the available methods (backup export, phpMyAdmin interface, script, SSH connection)|**Inbound migration**: [Importing a backup into a Web Hosting plan database](/pages/web_cloud/web_hosting/sql_importing_mysql_database)<br><br>[Private SQL - Importing a database](/pages/web_cloud/web_cloud_databases/starting_with_clouddb#importing-a-database-optional)<br><br>**Outbound migration**: [Retrieving the backup of a Web Hosting plan’s database](/pages/web_cloud/web_hosting/sql_database_export)| |
28 | 21 |
|
29 |
| -### OVHcloud implementation |
| 22 | +## 1. Core features |
30 | 23 |
|
31 |
| -|Feature|Description|Available formats|Migration model|Available documentation| |
32 |
| -|---|---|---|---|---| |
33 |
| -|1-click modules|Automated installation of CMS (WordPress, PrestaShop, Joomla!, Drupal)|N/A|**Inbound migration**: Not applicable<br><br>**Outbound migration**: Once the module is installed, follow the standard website migration procedure (including database migration)|**Outbound migration**: See "Web Hosting" above.| |
34 |
| -|Automatic Backups|Automated website and database backups|N/A, restore a backup to export its content|**Inbound migration**: Backups are automatically enabled.<br><br>**Outbound migration**: Enable a backup plan with the new provider after the site is migrated.<br><br>It is not possible to export a backup as such: backups are internal and are not presented as a file or archive. To import the contents of a file server and database, **restore the backup and then export the website** as shown above.|**Inbound migration**: See "Web Hosting" above.<br><br>**Outbound migration**: See "Web Hosting" above.| |
35 |
| -|Logging|Retention and browsing of the website logs. Analysis and graphic representation of these logs with the Urchin WebAnalytics application.|Plain text with standard apache log format|**Inbound migration**: Not applicable - logs from previous infrastructure are unlikely to be relevant to another.<br><br>**Outbound migration**: Download log files from the [OVHcloud Control Panel](/links/manager)|**Inbound migration**: N/A<br><br>**Outbound migration**: [Exporting a website - retrieving the logs](/pages/web_cloud/web_hosting/exporter-son-site-web#step-3-retrieve-the-logs-for-your-ovhcloud-web-hosting-plan)| |
36 |
| -|Job scheduling|Performing periodic automated tasks (cron)|N/A|**Inbound migration**: Scripts are not imported as is. Retrieve old scripts, or their business logic, and reimplement them on OVHcloud hosting through the [OVHcloud Control Panel](/links/manager).<br><br>**Outbound migration**: Scripts are not exported as is. Retrieve the business logic of the scripts in the [OVHcloud Control Panel](/links/manager) and reimplement them in the target environment.|**Inbound and outbound migration**: [Using automated tasks on a Web Hosting plan](/pages/web_cloud/web_hosting/cron_tasks)| |
| 24 | +| **Function** | **Description** | **Available formats** | **Migration model** | **Available documentation** | |
| 25 | +| --- | --- | --- | --- | --- | |
| 26 | +| Standard web hosting package | Use standard open-source components: Linux, Apache, MySQL/MariaDB, PHP | SQL, PHP, HTML, JSON, CSV | **Inbound**: copy of application files, import databases via SQL dump <br>**Outbound**: export data files/database dumps, reusable on any compatible environment | [How to create a Debian or Ubuntu web server](/pages/bare_metal_cloud/dedicated_servers/installing_lamp_debian9_ubuntu18) | |
| 27 | +| Import and export application files | Transfer web files (PHP, HTML, assets) via FTP/SFTP and rsync for professional and performance offers | All file formats | **Inbound**: Direct file upload <br>**Outbound**: Direct file export for migration to any other hosting provider | [Export your website](/pages/web_cloud/web_hosting/export-your-website) | |
| 28 | +| SSH/SFTP access to the client environment | Easy user access to your environment for file transfer and automation | Files, scripts, dumps | **Inbound**: application file transfer, SQL dumps, scripts via FTP/SFTP and rsync/scp/SSH for Professional and Performance plans <br>**Outbound**: export files, dumps, scripts via FTP/SFTP and rsync/scp/SSH for Professional and Performance plans to any other hosting provider| [Export your website](/pages/web_cloud/web_hosting/export-your-website) | |
37 | 29 |
|
38 |
| -### Specific functionalities |
| 30 | +## 2. OVHcloud Implementations |
39 | 31 |
|
40 |
| -|Feature|Description|Available formats|Migration model|Available documentation| |
41 |
| -|---|-----|---|-----|---| |
42 |
| -|Web application Firewall|HTTP Server Module for Filtering Inbound and Outbound Web Content|N/A|**Inbound migration**: Enabling the firewall from the [OVHcloud Control Panel](/links/manager).<br><br>**Outbound migration**: Order and configure a firewall with the new provider|**Inbound migration**: [Activating the application firewall](/pages/web_cloud/web_hosting/multisites_activating_application_firewall)<br><br>**Outbound migration**: N/A| |
43 |
| -|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](/links/security/antiddos)<br><br>**Outbound migration**: N/A| |
44 |
| -|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 the [OVHcloud Control Panel](/links/manager).<br><br>**Outbound migration**: Order and set up a load balancer with the new provider|**Inbound migration**: [OVHcloud Load Balancers](/links/network/load-balancer)<br><br>**Outbound migration**: N/A| |
| 32 | +| **Function** | **Description** | **Available formats** | **Migration model** | **Available documentation** | |
| 33 | +| --- | --- | --- | --- | --- | |
| 34 | +| Cron jobs and scheduled jobs | Automated tasks via crontab | NA | **Inbound**: recreating scheduled jobs on the target via the OVHcloud Control Panel or API <br>**Outbound**: export via API. Manual adaptation to be made in the target environment for tasks to be scheduled | [Create automated tasks](/pages/web_cloud/web_hosting/cron_tasks) | |
| 35 | +| Non-standard Apache/PHP modules | Modules or extensions not present on the target by default | Modules, extensions | **Inbound**: adaptation of applications to the hosting environment provided. Apache configuration, PHP available online <br>**Outbound**: check the availability of modules on the target, adaptation is possible | [Web hosting](/pages/web_cloud/web_hosting/web_hosting_main_info)<br><br>[Configure your hosting environment](/pages/web_cloud/web_hosting/configure_your_web_hosting) | |
| 36 | +| Synchronization with Git repositories | Synchronize data with Git repositories | All file types | **Inbound**: import data via configuration of a Git repository <br>**Outbound**: export data via configuration of a Git repository | [Configure and use Git](/pages/web_cloud/web_hosting/git_integration_webhosting) | |
45 | 37 |
|
46 |
| -### Architecture listing |
| 38 | +## 3. Specific features |
| 39 | + |
| 40 | +| **Function** | **Description** | **Available formats** | **Migration model** | **Available documentation** | |
| 41 | +| --- | --- | --- | --- | --- | |
| 42 | +| Monitoring | Dashboard for monitoring: FTP commands, http requests, average response time, outgoing connections, CPU usage, exceeding the resource limit | NA | **Inbound**: activation is automatic when the service is created, no action required <br>**Outbound**: NA | [View website statistics and logs](/pages/web_cloud/web_hosting/logs_and_statistics) | |
| 43 | +| Data analysis | Data analysis tool (OWSTAT) to generate a statistical follow-up on a given website | HTTP | **Inbound**: activation is automatic when the service is created, no action required <br>**Outbound**: no export possible | [View website statistics and logs](/pages/web_cloud/web_hosting/logs_and_statistics) | |
| 44 | +| Anti-DDoS protection| Anti-DDoS is a set of tools and mechanisms designed to absorb denial of service attacks. It includes traffic analysis, "clean-up" via a specialized network, and mitigation using VAC technology developed by OVHcloud. | N/A | **Inbound**: The anti-DDoS system is part of our infrastructure and is enabled by default. No action is required <br> **Outbound**: Order and configure an anti-DDoS solution from the new provider | [Anti-DDoS OVHcloud](/links/security/anti-ddos) | |
| 45 | + |
| 46 | +### List of architectures |
47 | 47 |
|
48 | 48 | All components of an OVHcloud Web product are accessible through the [OVHcloud Control Panel](/links/manager). This allows to visualize and manage the front-end web servers, file servers, databases, domain names, email, ... as well as the features that are attached to these components.
|
49 | 49 |
|
50 | 50 | ### Partner services
|
51 | 51 |
|
52 |
| -OVHcloud Partners are listed with the "Cloud Migration" keyword in the dedicated [directory](/links/partner). |
| 52 | +The OVHcloud partners concerned are listed in the [OVHcloud partners directory](/links/partner) under the "**Data center expansion and Migration**" keywords. |
| 53 | + |
| 54 | +OVHcloud also has a dedicated service: [OVHcloud Professional Services](/links/professional-services). |
53 | 55 |
|
54 | 56 | ### Cost and fees
|
55 | 57 |
|
56 |
| -No additional billing is planned from OVHcloud for the migration features listed here. |
| 58 | +Billing is per year. No specific cancelation fee applies: deletion of the service will stop billing on the anniversary date. It is the customer’s responsibility to export their files, databases and configurations before deletion, as deletion is irreversible. |
57 | 59 |
|
58 | 60 | ### Retention of data after contract termination
|
59 |
| - |
60 |
| -The data is retained 45 days after the termination of the service and then deleted permanently. |
| 61 | +After deleting the service or contract termination, OVHcloud permanently deletes all stored data (files, databases, snapshots). A retention period of 45 days following the service’s expiry date applies. |
0 commit comments