| title | excerpt | updated |
|---|---|---|
MySQL - Capabilities and Limitations |
Discover the capabilities and limitations of Public Cloud Databases for MySQL |
2025-02-19 |
This page provides the technical capabilities and limitations of the Public Cloud Databases' MySQL offer.
We continuously improve our offers. You can follow and submit ideas to add to our roadmap at https://github.com/orgs/ovh/projects/16/views/5.
The Public Cloud Databases offer is available in the following regions:
BHS(Beauharnois, Canada)DE(Frankfurt, Germany)GRA(Gravelines, France)SBG(Strasbourg, France)SGP(Singapore, Singapore)UK(London, United Kingdom)WAW(Warsaw, Poland)
Entire database instances have to be in the same region. Multi-AZ is currently not supported.
The Public Cloud Databases offer supports the following MySQL versions:
- MySQL 8.0
Please refer to the DBMS 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 API{.external} to access your cluster.
Three plans are available:
- Essential
- Business
- Enterprise
Here is an overview of the various plans' capabilities:
| Plan | Number of nodes by default | Read replicas | MySQL License |
|---|---|---|---|
| Essential | 1 | No | Community |
| Business | 2 | Planned | Community |
| Enterprise | 3 | Planned | Community |
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.
[!primary] Be aware that you will be able to upgrade your plan but you won't be able to downgrade it afterwards.
- 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 inside the service plans. You can't bring your own licenses.
For information on node types and pricing, please refer to the price page.
You can increase the storage of your cluster up to the maximum allowed for a given reference. Please refer to the Resize your cluster storage guide for more information.
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 Availability of Public Cloud products for more information about block storage type availability depending on 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 Block Storage documentation for more information about those performance characteristics.
Public Cloud Databases will select the most efficient disk type for your cluster 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 in the "DISK_FULL" state, and "read-only" mode, meaning no more writes can be done.
- You then have the ability to upgrade to a higher service plan with more storage.
See the Handling «Disk Full» situations documentation for more information.
MySQL clusters are reachable through default port 3306.
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.
Here are some considerations to take into account when using 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 Public 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.
- OpenStack subnets routes announcement will not be applied to your services.
- You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network.
Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorise incoming traffic. Until then, your service will be unreachable.
The number of simultaneous connections in Public Cloud Databases for MySQL depends on the available total memory on the node. We allow 75 connections per each 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 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 customise your MySQL by using advanced parameters. See the Advanced parameters references documentation for more information on the supported parameters.
Essential plan clusters are automatically backed up daily. Backup retention is 2 days.
Business plan clusters are automatically backed up daily. Backup retention is 14 days.
Enterprise plan clusters are automatically backed up daily. Backup retention is 30 days.
See the Automated Backups guide for more information.
Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. For setup instructions, see the Public Cloud Databases - How to setup logs forwarding guide.
- 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.
Creation of users is allowed via the Control Panel and API with default admin roles and privileges.
We would love to help answer questions and appreciate any feedback you may have.
If you need training or technical assistance to implement our solutions, contact your sales representative or click on this link to get a quote and ask our Professional Services experts for a custom analysis of your project.
Are you on Discord? Connect to our channel at https://discord.gg/ovhcloud and interact directly with the team that builds our databases service!