Skip to content

Commit b89fe51

Browse files
H4516022YH4516022Y
authored
Create guide.en-gb.md
1 parent 27bbd53 commit b89fe51

File tree

1 file changed

+87
-0
lines changed
  • pages/public_cloud/public_cloud_databases/reversbility/rdb_mysql_postgre

1 file changed

+87
-0
lines changed

‎pages/public_cloud/public_cloud_databases/reversbility/rdb_mysql_postgre/guide.en-gb.md

Lines changed: 87 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,87 @@
1+
# Reversibility Policy for Managed Relational Database Product
2+
3+
## Objective
4+
5+
This document outlines the reversibility policy for the product line Managed Relational Database covering OVHcloud offers : Managed MySQL & Managed PostgreSQL .
6+
7+
This policy aims to implement general reversibility principles and our compliance with the SWIPO IaaS Code of Conduct for cloud providers.
8+
9+
10+
11+
## List of Features
12+
13+
The features of the “Product” are divided into three categories:
14+
15+
- **Core features** for which we guarantee migration capability.
16+
- **OVHcloud implementations** that require adaptation to a new environment for migration.
17+
- **Specific features** that cannot be guaranteed for migration as they are tied to the OVHcloud environment or involve custom developments.
18+
19+
20+
21+
## Core Features
22+
23+
| Feature | Description | Formats | Migration Model | Documentation Available |
24+
|--------------------------|----------------------------------------------|---------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|
25+
| **Export/Import - PostgreSQL** | Use of `pg_dump`/`pg_restore` for native data transfer. | SQL, CSV, BINARY | Incoming: Restore via CLI with rights adjustments. <br> Outgoing: Standard dump export. | [OVH - How to migrate](https://support.us.ovhcloud.com/hc/en-us/articles/21485451623059-PostgreSQL-Tutorial-How-to-Migrate-an-On-Premises-Database-to-Cloud-Databases) |
26+
| **Export/Import - MySQL** | Export and import using native MySQL tools (`mysqldump`, `mysql`, etc.). | SQL, CSV | Incoming: Export from source (SQL dump), then import into Managed MySQL via `mysql` or OVHcloud UI. <br> Outgoing: SQL dump via `mysqldump`, then import into target environment (cloud or on-premises). | [MySQL - Capabilities and Limitations](https://support.us.ovhcloud.com/hc/en-us/articles/20887483746067-MySQL-Capabilities-and-Limitations) |
27+
| **Service Access - MySQL** | Access to the database via standard MySQL protocol on a dynamic port made available in the OVHcloud Manager. | N/A | Incoming: Connection from existing tools or applications. <br> Outgoing: Connect from any standard MySQL client for data extraction or migration. | [MySQL - Connect via Command Line (CLI)](https://support.us.ovhcloud.com/hc/en-us/articles/20805146473875-MySQL-Connect-with-CLI)<br>[MySQL - Connect with PHP](https://support.us.ovhcloud.com/hc/en-us/articles/20815696722963-MySQL-Connect-with-PHP)<br>[MySQL - Connect with Python](https://support.us.ovhcloud.com/hc/en-us/articles/20840434483219-MySQL-Connect-with-Python)<br>[MySQL - Connect with MySQL Workbench](https://support.us.ovhcloud.com/hc/en-us/articles/20845437747987-MySQL-Connect-with-MySQL-Workbench)|
28+
| **Service Access - PostgreSQL**| Access via PostgreSQL protocol, compatible with standard clients and tools. | N/A | Incoming: Direct connection from existing tools/applications. <br> Outgoing: Standard connection for extraction or migration. | [PostgreSQL - Connect via Command Line (CLI)](https://support.us.ovhcloud.com/hc/en-us/articles/21410499182995-PostgreSQL-Connect-with-CLI)<br>[PostgreSQL - Connect with PHP](https://support.us.ovhcloud.com/hc/en-us/articles/20898939497107-PostgreSQL-Connect-with-PHP)<br>[PostgreSQL - Connect with Python](https://support.us.ovhcloud.com/hc/en-us/articles/21408187602451-PostgreSQL-Connect-with-Python)<br>[PostgreSQL - Connect with pgAdmin](https://support.us.ovhcloud.com/hc/en-us/articles/21489279019155-PostgreSQL-Connect-with-pgAdmin)|
29+
| **Manual Backup** | Ability to generate a full on-demand database backup. | SQL, CSV, tar | Incoming: Restore from existing SQL dump. <br> Outgoing: SQL dump generated from OVHcloud instance, usable on any compatible MySQL environment. | [MySQL dump](https://dev.mysql.com/doc/refman/8.4/en/mysqldump.html) |
30+
31+
32+
## OVHcloud Implementation
33+
34+
| Feature | Description | Available Formats | Migration Model | Documentation Available |
35+
|------------------|-------------------------------------------------------------------------------------------------------------------|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|
36+
| **OVHcloud Automatic Backups** | Backups managed by OVHcloud, not directly exportable outside the OVH ecosystem. | Internal snapshots | Incoming: Not applicable for direct import. <br> Outgoing: Requires restoration on OVHcloud instance, then manual export (SQL dump) for migration. | [Databases & Analytics - Automated backups](https://support.us.ovhcloud.com/hc/en-us/articles/20735484294547-Databases-Analytics-Automated-backups) |
37+
| **Point in Time Recovery (PITR)**| Restore to a specific point in time using OVHcloud internal snapshots. | Internal snapshots | Incoming: Not applicable for direct import, prior restoration required. <br> Outgoing: Export restored snapshot as SQL dump, then manual import in target environment. | [Databases & Analytics - Automated backups](https://support.us.ovhcloud.com/hc/en-us/articles/20735484294547-Databases-Analytics-Automated-backups) |
38+
| **OVHcloud API** | Manage databases via OVHcloud REST API or graphical interface. | N/A | Incoming: Automated creation and import of instances. <br> Outgoing: Data export via API or automated dump scripts. |[Premiers pas avec les API OVHcloud](https://help.ovhcloud.com/csm/fr-api-getting-started-ovhcloud-api?id=kb_article_view&sysparm_article=KB0042789) |
39+
| **OVHcloud Connection Pooling** | Automatic PostgreSQL connection pooling, not directly portable. | N/A | Incoming: May require adaptation depending on source setup. <br> Outgoing: Pooling must be reconfigured on target infrastructure. | [PostgreSQL - Create and Use Connection Pools](https://support.us.ovhcloud.com/hc/en-us/articles/21419624594323-PostgreSQL-Create-and-Use-Connection-Pools) |
40+
| **Observability** | Metrics collection via OVHcloud-integrated Prometheus. | Prometheus metrics | Incoming: Adapt dashboards and metrics to OVHcloud environment. <br> Outgoing: Metrics export possible, requires adaptation on new monitoring platform. | [MySQL - Capabilities and Limitations](https://support.us.ovhcloud.com/hc/en-us/articles/20887483746067-MySQL-Capabilities-and-Limitations)<br>[PostgresSQL – Capabilities and Limitations](https://support.us.ovhcloud.com/hc/en-us/articles/21485451623059-PostgreSQL-Tutorial-How-to-Migrate-an-On-Premises-Database-to-Cloud-Databases) |
41+
| **vRack** | Virtual rack (vRack) is a private VLAN technology that connects OVHcloud services. | N/A | **Inbound:** MySQL and PostgreSQL services are included in vRack by default. <br> **Outbound:** Record the network architecture and replicate it using VLANs. | [V(x)LAN creation](https://help.ovhcloud.com/csm/fr-vmware-vlan-creation?id=kb_article_view&sysparm_article=KB0045480)<br>[Public Cloud Databases](https://help.ovhcloud.com/csm/fr-public-cloud-databases-configure-vrack?id=kb_article_view&sysparm_article=KB0048824) |
42+
| **Role and Permission Adaptation**| No superuser (e.g., `postgres`); roles must be adapted to `avnadmin` or equivalent. | N/A | Incoming: Modify dump to replace superuser roles with OVH-compatible roles. <br> Outgoing: Reverse adaptation based on target environment privileges. | [PostgresSQL – Capabilities and Limitations](https://support.us.ovhcloud.com/hc/en-us/articles/21485451623059-PostgreSQL-Tutorial-How-to-Migrate-an-On-Premises-Database-to-Cloud-Databases) |
43+
| **OVHcloud ACL Management** | Access rights managed through OVHcloud interface. | N/A | Incoming: Manually recreate rules in the OVHcloud interface. <br> Outgoing: Convert ACL rules to the new provider’s format. | [MySQL - Capabilities and Limitations](https://support.us.ovhcloud.com/hc/en-us/articles/20887483746067-MySQL-Capabilities-and-Limitations)<br>[PostgresSQL – Capabilities and Limitations](https://support.us.ovhcloud.com/hc/en-us/articles/21485451623059-PostgreSQL-Tutorial-How-to-Migrate-an-On-Premises-Database-to-Cloud-Databases) |
44+
45+
46+
## Specific Features
47+
48+
| Function | Description | Formats Available | Migration Model | Documentation Available |
49+
|------------------------|---------------------------------------------------------------------------------------|--------------------|----------------------------------------------------------------------------------------------------|--------------------------|
50+
| **OVHcloud Database Forking** | Instant duplication of a database via OVHcloud's native "fork" feature. | OVHcloud internal | Incoming: Feature not available for import. <br> Outgoing: Not portable — requires manual data export to replicate elsewhere. | [Databases & Analytics - Restore a backup](https://support.us.ovhcloud.com/hc/en-us/articles/20584170298515-Databases-Analytics-Restore-a-backup) |
51+
| **Infrastructure as Code** | Automated deployment via OVHcloud-specific Terraform modules | N/A | **Inbound migration:** Scripts need to be adapted for other providers. <br> **Outbound migration:** Configuration rewrite required for Terraform. | [Terraform](https://registry.terraform.io/providers/ovh/ovh/latest/docs) |
52+
| **OVHcloud-Managed Updates** | MySQL or PostgreSQL versioning and updates are managed by OVHcloud. | N/A | Incoming: Ensure compatibility. <br> Outgoing: Migration responsibility falls to the customer. | [MySQL - Capabilities and Limitations](https://support.us.ovhcloud.com/hc/en-us/articles/20887483746067-MySQL-Capabilities-and-Limitations)<br>[PostgresSQL – Capabilities and Limitations](https://support.us.ovhcloud.com/hc/en-us/articles/21485451623059-PostgreSQL-Tutorial-How-to-Migrate-an-On-Premises-Database-to-Cloud-Databases) |
53+
| **Anti-DDoS** | Anti-DDoS is a set of tools and mechanisms designed to absorb denial-of-service attacks. It includes traffic analysis, "scrubbing" through a specialized network, and mitigation handled by the VAC technology developed by OVHcloud. | N/A | **Inbound migration:** The anti-DDoS system is part of our infrastructure and is enabled by default. No action is required. <br> **Outbound migration:** Order and configure an anti-DDoS service with the new provider. | [Anti-DDoS Protection](https://www.ovh.com/fr/anti-ddos/)<br>[Anti-DDoS technologie](https://www.ovh.com/fr/anti-ddos/technologie-anti-ddos.xml) |
54+
55+
56+
57+
## List of Architectures
58+
59+
**OVHcloud’s Managed MySQL and Managed PostgreSQL** support different architectures depending on the selected service tier.
60+
The **“Business”** and **“Enterprise”** plans offer **high availability** with multiple nodes and **automatic asynchronous replication**.
61+
62+
63+
64+
## Partner Services
65+
66+
OVHcloud partners are listed under the keyword **"Cloud Migration"** in the dedicated partner directory.
67+
68+
OVHcloud also offers a dedicated service: [**OVHcloud Professional Services**](https://www.ovhcloud.com/fr/professional-services/).
69+
70+
71+
72+
## Cost and Fees
73+
74+
- **No termination fees**: There are no additional charges related to data migration by default.
75+
- Billing stops as soon as the service is terminated.
76+
77+
78+
79+
## Data Retention After Contract Termination
80+
81+
OVHcloud **does not retain any data** after a Managed Data Visualization cluster is deleted.
82+
Both **automatic and manual snapshots are permanently deleted**.
83+
A **manual export** must be performed in advance if data needs to be preserved.
84+
Primary instances are **deleted immediately**, and **backups are retained for a period ranging from 2 days to 1 month**
85+
> **Important:** Clients cannot rely on these backups for data restoration.
86+
> OVH does not guarantee the usability or availability of backups for restoring customer data after the termination of the service.
87+

0 commit comments

Comments
 (0)