(Important) Increasing your database capacities

For Turbonomic versions 8.0.6 or later, your historical database must provide certain storage size capacities. For MariaDB or MySQL installations, your database must provide the necessary memory, messaging, and logging capacity.

For its historical database, Turbonomic supports long-term maintenance stable series of MariaDB (the minimum supported version is 10.6) and MySQL 8.0.x. This support includes comprehensive testing and quality control for Turbonomic usage.

For details, see Verifying your MariaDB Version, Configuring a Remote Database.

Note:

If you installed Turbonomic as a VM image (OVA or VHD), the image includes MariaDB for the historic database. Most installations use that instance. However, you can use an external database if you like. In addition, you can install Turbonomic directly to a Red Hat OpenShift or Kubernetes cluster (instead of installing the VM image), and you can provide your own historical database.

To install Turbonomic on an existing cluster, your environment must meet the following requirements.

Increase DB capacities

The way that you deploy the historical database in your Turbonomic installation determines whether you must increase your database capacities.

For this installation	DB storage update requirements
You installed Turbonomic as a VM image at version 8.0.6 or earlier. You are using the default MariaDB as your historical database. You updated Turbonomic to version 8.0.7 or later You ran the script that updates your MariaDB version (see Verifying your MariaDB Version).	You do not need to increase your DB capacities. You can skip this procedure. Note: If you are still running MariaDB 10.5.6 or 10.5.9, you must update to 10.6.19. See Verifying your MariaDB Version.
You installed Turbonomic as a VM image at version 8.0.6 or earlier. You are using the default MariaDB as your historical database. You have not updated Turbonomic to version 8.0.7 or later. You have not run the script that updates your MariaDB version (see Verifying your MariaDB Version).	Increase your DB capacities. Note: The simplest way to increase capacities and ensure that you are running the correct version of MariaDB is to update Turbonomic the latest version (see Updating Turbonomic to a New Version).
You installed Turbonomic as a VM image. You are using an external MariaDB or MySQL as your historical database.	Increase your DB capacities.
You installed Turbonomic directly on a Kubernetes cluster (not deployed as the Turbonomic VM image) You are using MariaDB or MySQL as your historical database.	Increase your DB capacities.

Checking your current DB capacities

Before you update your DB capacities, check to make sure that they need to be increased. Open an SSH terminal session that can administer your database, and run the following commands:

Check the size for max_allowed_packet.
```
mysql -u root -p vmtdb
```
Enter your password when prompted and then run the following command.
```
SHOW VARIABLES LIKE 'max_allowed_packet';
```
The output is similar to the following example:
```
+--------------------+--------------+
| max_allowed_packet | <PacketSize> |
+--------------------+--------------+
```
Where <PacketSize> is your current value. If it is greater than or equal to 1073741824, you do not need to increase this capacity.
Check the size for innodb_log_file_size.
```
SHOW VARIABLES LIKE 'innodb_log_file_size';
```
The output is similar to the following example:
```
+----------------------+-------------+
| innodb_log_file_size |  <LogSize>  |
+----------------------+-------------+
```
Where <LogSize> is your current value. If it is greater than or equal to 10737418240 (10 times the max allowed packet size), you do not need to increase this capacity.

Configuring the capacities

Edit your database server's configuration file to set the following server system variables.

Open the configuration file in an editor, change the values for these system variables, and then save your changes.

For MariaDB, depending on the Operating System, you find the configuration file at /etc/server.cnf or /etc/my.cnf.d/server.cnf.
- max_allowed_packet = 1G
- innodb_log_file_size = 10G
- innodb_buffer_pool_size = <see the following note>
Note:
The innodb_buffer_pool_size must be at least 4096 M (or 4G). Increase the value to support larger topologies. Refer to the following table for suggested values based on system memory.

System memory (mem) innodb_buffer_pool_size

mem <= 32GB 4G

mem > 32GB and mem <= 64GB 8G

mem > 64GB and mem <= 128GB 16G

mem > 128GB 32G
Restart your DB instance.
- With Rocky 9.3, the following command restarts MariaDB:
```
systemctl restart mariadb.service
```
- With Rocky 9.3, the following command restarts MySQL:
```
systemctl restart mysqld.service
```

System memory (mem)	innodb_buffer_pool_size
`mem <= 32GB`	`4G`
`mem > 32GB and mem <= 64GB`	`8G`
`mem > 64GB and mem <= 128GB`	`16G`
`mem > 128GB`	`32G`

After the database restarts, verify the system capacity.

mysql -u root -p vmtdb

Enter your password when prompted and then run the following commands.

SHOW VARIABLES LIKE 'max_allowed_packet';

The output is similar to the following example:

+--------------------+------------+
| Variable_name      | Value      |
+--------------------+------------+
| max_allowed_packet | 1073741824 |
+--------------------+------------+

SHOW VARIABLES LIKE 'innodb_log_file_size';

The output is similar to the following example:

+----------------------+-------------+
| Variable_name        | Value       |
+----------------------+-------------+
| innodb_log_file_size | 10737418240 |
+----------------------+-------------+