FAQ

DBaaS is only available on Virtual Servers at this time. There may be support for Cloud Cubes in the future.

Depending on the library you are using, you may see an error message similar to the following:

Too many connections

As each user has 250 connections and max_connections is set to 500, it is less probable that a user will use up all of their connections with MariaDB.

Unfortunately, it is not allowed to scale the deployment for increasing connection limits.

IONOS CLOUD provides an automated backup within the cloud infrastructure. You can use the mariadb-dump client to back up data to a different location. For more information, refer to the MariaDB Documentation.

Achieving high availability and minimal latency are the main goals of the IONOS CLOUD. We recommend that you host your application servers closer to your database and in a geographic location appropriate for your user base to reduce the adverse effects of network latency on your application. For more information, refer to the MariaDB Documentation.

The MariaDB v2 API is a managed REST interface for provisioning and managing fully managed MariaDB clusters. It uses token-based authentication and supports clusters with a single primary instance and up to four secondary instances for high availability.

The MariaDB v2 API requires token-based authentication. Include a Bearer token in the Authorization header of each request. You can generate a token using the Authentication API.

PUT /clusters/{clusterId} is an idempotent "Ensure" operation. If a cluster with the provided ID does not exist, it is created. If it already exists, it is updated to match the provided payload. Any properties not included in the request are filled with defaults or left empty; previous values are not retained.

The initial database user password must meet the following requirements:

MariaDB v2 continuously archives binary logs and performs periodic full backups, enabling Point-in-Time Recovery (PITR). You can restore a cluster to any specific moment within the available backup window.

To restore from a backup when creating a new cluster, use sourceBackupId in the restoreFromBackup property. To optionally target a specific point in time, provide recoveryTargetDatetime as an ISO 8601 timestamp. For in-place restore on an existing cluster, provide recoveryTargetDatetime only; the restore source is inferred from the cluster's own backups. Note that in-place restore overwrites current data and may cause a brief period of downtime.

When creating or updating a cluster, set the backup.location property to an Object Storage location returned by GET /backup-locations. For added data safety, use a location different from the one hosting the cluster. You can also set backup.retentionDays to control how long backups are kept (1–365 days).

List endpoints support offset and limit query parameters for pagination (maximum 1000 items per page). You can also filter clusters by name (filter.name) and state (filter.state), and filter backups by cluster ID (filter.clusterId).

Set logsEnabled to true to enable collection and reporting of logs, and set metricsEnabled to true to enable collection and reporting of metrics. Note that the observability service must be activated on your contract for these settings to take effect.

A maintenance window is a weekly 4-hour slot during which IONOS CLOUD may apply updates or patches. You configure it with a dayOfTheWeek and a UTC start time in the maintenanceWindow property when you create or update a cluster. Only one maintenance window can be configured per cluster.

Use GET /versions to retrieve all supported MariaDB versions, their support status (BETA, SUPPORTED, RECOMMENDED, or DEPRECATED), and the versions each can be upgraded to.