For the complete documentation index, see llms.txt. This page is also available as Markdown.

Create MariaDB Cluster

Using this guide, you can create a MariaDB cluster in the DCD using the new v2 infrastructure.

Prerequisites: Before setting up a database, make sure you are working within a provisioned VDC that contains at least one virtual machine from which to access the database. The VM you create is counted against the quota allocated in your contract.

Note: Database Manager is available only for contract administrators, owners, and users with Access and manage DBaaS privilege. You can set the privilege through the DCD group privileges.

1

1. In the DCD, go to Menu > Databases > MariaDB.

2. From the MariaDB cluster overview page, click Create cluster.

MariaDB cluster overview
2

Define cluster properties

In the Properties section, specify the following:

1. Cluster name: Enter a name for the cluster.

2. Location: Select the region where the cluster is deployed, for example Germany / Berlin (de/txl). Each cluster is bound to a region-specific API endpoint, and the location you select determines which endpoint manages the cluster. This cannot be changed after the cluster is created.

3. (Optional) Description: Enter a human-readable description for the cluster.

Define cluster properties
3

Configure the cluster

In the Cluster configuration section, enter the following details:

1. Version: Select the MariaDB version for the cluster. IONOS CLOUD supports MariaDB Long-Term Support (LTS) versions, starting from MariaDB 10.6, for example 10.6 or 10.11.

2. Instances: Enter the number of instances in the cluster. A value of 1 creates a single-instance cluster. Values 2–5 create a replicated cluster with one primary and n-1 secondary instances. You can create a maximum of five instances within a cluster.

Note: Replication between the primary and secondary instances is always asynchronous. The primary instance does not wait for a secondary to confirm the data has been written, so the cluster can lose some committed transactions to ensure availability.

3. Backup: Select the Object Storage region where cluster backups are stored, for example eu-central-3.

Note: For geographic data safety, consider choosing a backup location that differs from the cluster's own region.

4. Retention days: Enter the number of days backups are retained before being automatically deleted. You can set a value between 1 and 365.

Configure the cluster
4

(Optional) Restore from a backup

To initialize the new cluster with data from an existing backup, go to the Restore configuration section and select Restore cluster from backup, then specify the following:

1. Source backup: Select the backup to restore from.

2. Recovery target datetime: Select a date and time within the displayed recovery window. The cluster is restored from the backup data up to that point in time. If left empty, the backup is applied in its entirety.

Note: A restored backup also includes its stored credentials; credentials you provide later in User Creation override those from the backup.

Restore configuration
5

Configure Observability

In the Observability section, you can turn on the following:

1. Enable logs: Turn on to forward cluster logs to your logging endpoint.

2. Enable metrics: Turn on to forward cluster metrics to your monitoring endpoint.

Note: Both settings are turned off by default. Observability services must be activated for your contract before logs and metrics can be collected; if not activated, these settings are accepted but have no effect until the service is activated.

Configure Observability
6

Select the required number of resources

In the Resources section, specify the number of resources to associate with the cluster, per instance:

1. Number of CPUs (per instance): Select the number of dedicated CPU cores using the slider.

2. RAM Size (per instance): Select the amount of RAM, in GB, using the slider.

3. Storage Size (per instance): Select the amount of storage, in GB, using the slider. Storage size can only be increased after the cluster is created; it cannot be reduced.

The totals shown below each slider (for example, 12 CPUs in total) reflect the combined resources across all instances in the cluster.

Select the required number of resources
7

Connect the data center with the cluster

In the Data Center connection section, provide the following information to connect your cluster with the datacenter:

1. Network configuration: Select a datacenter from the available list.

2. VDC LAN: Select a LAN for your datacenter.

3. Private IP address: Enter the private IP address for the cluster's primary instance, in CIDR notation. For more information, see Private IP Address Ranges.

Note: Make sure the selected private IP address is not already in use within the DCD. The following IP address ranges cannot be used with MariaDB services:

  • 10.208.0.0/12

  • 10.233.0.0/18

  • 192.168.230.0/24

  • 10.233.64.0/18

Connect the data center to the MariaDB cluster
8

Set the maintenance window

In the Maintenance Period section, you can set a maintenance day and time:

1. Day: Select a day from the drop-down list, for example Sunday.

2. Start Time (UTC): Enter a start time for the maintenance window.

Note: The maintenance timeframe is your selected start time (UTC) plus 4 hours. If not specified, the timeframe for maintenance can be anytime Mon - Fri, 7 AM - 5 PM.

Set the maintenance window
9

Create the database user

In the User Creation section, provide the following details:

1. Username: Enter a username to provide access to the MariaDB cluster.

2. Password: Enter a password for the respective user.

3. Database: Enter a name for the initial database to be created.

Create the database user

Note: Estimated costs are calculated and displayed based on the configuration entered so far. This estimate is exclusive of certain variables, such as traffic, which are not considered.

10

Save the cluster

Click Save to create the MariaDB cluster.

MariaDB cluster creation started

Next steps

Last updated

Was this helpful?