This page provides the technical capabilities and limitations of the Managed Databases (also called Cloud Databases) MySQL offer.
We continuously improve our offers. You can follow and submit ideas to add to our roadmap.
Capabilities and limitations
To view Cloud Databases availability, please see our regions and availability webpage.
Entire database instances have to be in the same region.
The Cloud Databases offer supports the following MySQL versions:
- MySQL 8.0
Please refer to our Cloud Databases - Lifecycle Policy guide for recommendations on version upgrades and end-of-life announcements of major versions. MySQL recommends always installing and using the latest stable version.
You can use any of the MySQL-recommended connectors and APIs to access your cluster.
Three plans are available:
Here is an overview of the various plans' capabilities:
|Number of nodes by default
Your choice of plan affects the number of nodes your cluster can run, the SLA, and a few other features such as read replicas or backup retention.
Nodes and replicas
- Essential: the cluster can support at most one node.
- Business: the cluster is delivered with 2 nodes by default. Adding read replicas is planned.
- Enterprise: The cluster is delivered with 3 nodes by default. Adding read replicas is planned.
Each cluster is provided with the MySQL Community (GPL) license.
If any, license cost is included in the service plans. You can't bring your own licenses.
Here are the node types you can choose from:
|From 80 GB to 240 GB
|From 160 GB to 480 GB
|From 320 GB to 960 GB
|From 640 GB to 1.92 TB
|From 1.28 TB to 3.84 TB
|From 2.56 TB to 7.68 TB
Right now, all nodes of a given cluster should be of the same type and live in the same region.
You can increase the storage of your cluster up to the maximum allowed for a given reference. Please refer to our Cloud Databases - Resize Your Cluster Storage guide for more information.
Node template upgrade
You can upgrade the node template of your cluster to scale your hardware resources up. This operation causes no interruption of service but be aware that you will not be able to downgrade the node template afterwards.
The type of storage available may vary according to the region your cluster lives in: see our Availability of Public Cloud products page for more information about block storage type availability depending on the region. Thus, your cluster may be backed by e.g. High Speed or High Speed Gen2 block storage.
Also, the performance characteristics of the various storage offerings may vary depending on e.g. the storage size your cluster uses: High Speed may offer better iops than High Speed Gen2 for some disk sizes. See our Block Storage webpage for more information about those performance characteristics.
Cloud Databases will select your cluster's most efficient disk type depending on your cluster parameters.
The disk size listed above is the total disk size of the underlying machine. However, a small part of it goes towards the OS install.
We try hard to avoid "disk full" situations that could be harmful to cluster health. Therefore:
- When reaching a concerning level of disk usage, a warning email is sent.
- When reaching a concerning level of disk usage, the service is moved to the "DISK_FULL" state, and "read-only" mode, meaning no more writes can be done.
- You then can upgrade to a higher service plan with more storage.
See our Cloud Databases - Handling «Disk Full» Situations guide for more information.
MySQL clusters are reachable through the port defined in the OVHcloud Control Panel.
Public as well as private networking (vRack) can be used for all the offers.
Ingress and Egress traffic are included in the service plans and unmetered.
The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management.
Private network considerations
Here are some considerations to take into account when using a private network:
- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Cloud Databases services first.
- When connecting from an outside subnet, the OpenStack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup.
- Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services.
Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorize incoming traffic. Until then, your service will be unreachable.
Maximum simultaneous connections
The number of simultaneous connections in Cloud Databases for MySQL depends on the available total memory on the node. We allow 75 connections per GB of usable memory. Usable memory is the total memory on the node minus operating system and management overhead, which is currently estimated at 350 MiB. The usable memory is rounded to the nearest gigabyte.
So for example on a server with 7 GB memory, you will get 7 * 75 = 525 connections and with 15 GB memory, you will get 14 * 75 = 1050 connections. Note that the MySQL max-connections setting is always set to one higher (e.g. 526 / 1051 in the example cases) because there is usually one system process that consumes one of the available connections.
You can further customize your MySQL by using advanced parameters. See our MySQL - Advanced Parameters References documentation for more information on the supported parameters.
Essential plan clusters are automatically backed up daily during their maintenance window. Backup retention is 2 days.
Business plan clusters are automatically backed up daily during their maintenance window. Backup retention is 14 days.
Enterprise plan clusters are automatically backed up daily during their maintenance window. Backup retention is 30 days.
See our Cloud Databases - Automated Backups guide for more information.
Logs and metrics
Logs and metrics are available through the Control Panel and the API. Additionally, cross-service integration can be configured to leverage your logs and metrics in other Cloud Database services. You could then view your MySQL logs in OpenSearch and metrics in Grafana (metrics have to be exported first in a time series compatible engine such as PostgreSQL or M3db). See our Cloud Databases - Cross Service Integration guide for more information.
- Logs retention: 1000 lines of logs
- Metrics retention: 1 calendar month
Please note that if the database instance is deleted, logs and metrics are also automatically deleted.
Users and roles
Creation of users is allowed via the Control Panel and API with default admin roles and privileges.