---
title: "Reversibility Policy for Managed Relational Database Product"
url: https://docs.ovhcloud.com/it/guides/account-and-service-management/reversibility/rdb-mysql-postgre
lang: it
lastUpdated: 2025-06-12
---
# Reversibility Policy for Managed Relational Database Product
## Objective
This document outlines the reversibility policy for the product line Managed Relational Database covering following OVHcloud offers : Managed MySQL and Managed PostgreSQL.
This policy aims to implement general reversibility principles and our compliance with the SWIPO IaaS Code of Conduct for cloud providers.
## List of Features
Features of the product line Managed Relational Database are divided into three categories:
1. **Core features** for which we guarantee migration capability.
2. **OVHcloud implementations** that require adaptation to a new environment for migration.
3. **Specific features** that cannot be guaranteed for migration as they are tied to the OVHcloud environment or involve custom developments.
### 1 - Core features
| **Feature** | **Description** | **Available Formats** | **Migration Model** | **Available documentation** |
| --------------------------- | ------------------------------------------------------------------------------------------------------------ | --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Export/Import - PostgreSQL | Use of `pg_dump`/`pg_restore` for native data transfer. | SQL, CSV, BINARY | **Incoming**: Restore via CLI with rights adjustments.
**Outgoing**: Standard dump export. | [PostgreSQL - Tutorial - How to migrate an on-premises database to Public Cloud Databases](/it/guides/public-cloud/databases/postgresql-tuto-migrate-ecdb.md) |
| 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.
**Outgoing**: SQL dump via `mysqldump`, then import into target environment (cloud or on-premises). | [MySQL - Capabilities and Limitations](/it/guides/public-cloud/databases/mysql-capabilities.md) |
| 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.
**Outgoing**: Connect from any standard MySQL client for data extraction or migration. | [MySQL - Connect with CLI](/it/guides/public-cloud/databases/mysql-connect-cli.md)
[MySQL - Connect with PHP](/it/guides/public-cloud/databases/mysql-connect-php.md)
[MySQL - Connect with Python](/it/guides/public-cloud/databases/mysql-connect-python.md)
[MySQL - Connect with MySQL Workbench](/it/guides/public-cloud/databases/mysql-connect-workbench.md) |
| Service Access - PostgreSQL | Access via PostgreSQL protocol, compatible with standard clients and tools. | N/A | **Incoming**: Direct connection from existing tools/applications.
**Outgoing**: Standard connection for extraction or migration. | [PostgreSQL - Connect with CLI](/it/guides/public-cloud/databases/postgresql-connect-cli.md)
[PostgreSQL - Connect with PHP](/it/guides/public-cloud/databases/postgresql-connect-php.md)
[PostgreSQL - Connect with Python](/it/guides/public-cloud/databases/postgresql-connect-python.md)
[PostgreSQL - Connect with pgAdmin](/it/guides/public-cloud/databases/postgresql-connect-pgadmin.md) |
| Manual Backup | Ability to generate a full on-demand database backup. | SQL, CSV, tar | **Incoming**: Restore from existing SQL dump.
**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) |
### 2 - OVHcloud Implementations
| **Feature** | **Description** | **Available Formats** | **Migration Model** | **Available documentation** |
| ------------------------------ | ----------------------------------------------------------------------------------- | --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| OVHcloud Automatic Backups | Backups managed by OVHcloud, not directly exportable outside the OVH ecosystem. | Internal snapshots | **Incoming**: Not applicable for direct import.
**Outgoing**: Requires restoration on OVHcloud instance, then manual export (SQL dump) for migration. | [Public Cloud Databases - Automated Backups](/it/guides/public-cloud/databases/backups.md)
[Analytics - Automated Backups](/it/guides/public-cloud/data-analytics/analytics/backups.md) |
| 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.
**Outgoing**: Export restored snapshot as SQL dump, then manual import in target environment. | [Public Cloud Databases - Automated Backups](/it/guides/public-cloud/databases/backups.md)
[Analytics - Automated Backups](/it/guides/public-cloud/data-analytics/analytics/backups.md) |
| OVHcloud API | Manage databases via OVHcloud REST API or graphical interface. | N/A | **Incoming**: Automated creation and import of instances.
**Outgoing**: Data export via API or automated dump scripts. | [First Steps with the OVHcloud APIs](/it/guides/manage-and-operate/api/first-steps.md) |
| OVHcloud Connection Pooling | Automatic PostgreSQL connection pooling, not directly portable. | N/A | **Incoming**: May require adaptation depending on source setup.
**Outgoing**: Pooling must be reconfigured on target infrastructure. | [PostgreSQL - Create and Use Connection Pools](/it/guides/public-cloud/databases/postgresql-pool.md) |
| Observability | Metrics collection via OVHcloud-integrated Prometheus. | Prometheus metrics | **Incoming**: Adapt dashboards and metrics to OVHcloud environment.
**Outgoing**: Metrics export is possible, requires adaptation on new monitoring platform. | [MySQL - Capabilities and Limitations](/it/guides/public-cloud/databases/mysql-capabilities.md)
[PostgreSQL - Capabilities and Limitations](/it/guides/public-cloud/databases/postgresql-capabilities.md) |
| vRack | Virtual rack (vRack) is a private VLAN technology that connects OVHcloud services. | N/A | **Incoming**: MySQL and PostgreSQL services are included in vRack by default.
**Outgoing**: Record the network architecture and replicate it using VLANs. | [How to create a VLAN](/it/guides/hosted-private-cloud/powered-by-vmware/create-vlan.md)
[Public Cloud Databases - How to configure your Private Network](/it/guides/public-cloud/databases/configure-vrack.md) |
| 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 OVHcloud-compatible roles.
**Outgoing**: Reverse adaptation based on target environment privileges. | [PostgreSQL - Tutorial - How to migrate an on-premises database to Public Cloud Databases](/it/guides/public-cloud/databases/postgresql-tuto-migrate-ecdb.md) |
| OVHcloud ACL Management | Access rights managed through OVHcloud interface. | N/A | **Incoming**: Manually recreate rules in the OVHcloud interface.
**Outgoing**: Convert ACL rules to the new providers format. | [MySQL - Capabilities and Limitations](/it/guides/public-cloud/databases/mysql-capabilities.md)
[PostgreSQL - Capabilities and Limitations](/it/guides/public-cloud/databases/postgresql-capabilities.md) |
### 3 - Specific features
| **Feature** | **Description** | **Available Formats** | **Migration Model** | **Available documentation** |
| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| OVHcloud Database Forking | Instant duplication of a database via OVHcloud's native "fork" feature. | OVHcloud internal | **Incoming**: Feature not available for import.
**Outgoing**: Not portable, requires manual data export to replicate elsewhere. | [Public Cloud Databases - How to restore a backup](/it/guides/public-cloud/databases/restore-backup.md)
[Analytics - How to restore a backup](/it/guides/public-cloud/data-analytics/analytics/restore-backup.md) |
| Infrastructure as Code | Automated deployment via OVHcloud-specific Terraform modules. | N/A | **Incoming**: Scripts need to be adapted for other providers.
**Outcoming**: Configuration rewrite required for Terraform. | [Terraform](https://registry.terraform.io/providers/ovh/ovh/latest/docs) |
| OVHcloud-Managed Updates | MySQL or PostgreSQL versioning and updates are managed by OVHcloud. | N/A | **Incoming**: Ensure compatibility.
**Outgoing**: Migration responsibility falls to the customer. | [MySQL - Capabilities and Limitations](/it/guides/public-cloud/databases/mysql-capabilities.md)
[PostgreSQL - Capabilities and Limitations](/it/guides/public-cloud/databases/postgresql-capabilities.md) |
| 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 | **Incoming:** The anti-DDoS system is part of our infrastructure and is enabled by default. No action is required.
**Oucoming:** Order and configure an anti-DDoS service with the new provider. | [Anti-DDoS Protection](https://www.ovhcloud.com/it/security/anti-ddos/) |
## List of Architectures
**Managed MySQL and Managed PostgreSQL** support different architectures depending on the selected service tier.
The **Business** and **Enterprise** plans offer **high availability** with multiple nodes and **automatic asynchronous replication**.
## Partners Services
The OVHcloud partners concerned are listed in the [OVHcloud partners](https://partner.ovhcloud.com/it/directory/) directory under the **"cloud migration"** keywords.
OVHcloud also offers a dedicated service: [OVHcloud Professional Services](https://www.ovhcloud.com/it/professional-services/).
## Cost and Fees
- **No termination fees**: There are no additional charges related to data migration by default.
- Billing stops as soon as the service is terminated.
## Data Retention After Contract Termination
:::warning
OVHcloud does not guarantee the usability or availability of backups for restoring customer data after the termination of the service.
:::
OVHcloud **does not retain any data** after a Managed Data Visualization cluster is deleted.
Both **automatic and manual snapshots are permanently deleted**.
A **manual export** must be performed in advance if data needs to be preserved.
Primary instances are **deleted immediately**, and **backups are retained for a period ranging from 2 days to 1 month** depending on the options specified in the contract.