Corruption Diagnostic Add-On
MySQL / MariaDB / Percona Corruption Diagnostic Add-On
The Database Corruption Diagnostic add-on works with MySQL, MariaDB, and Percona databases, including supported cluster topologies. It checks the integrity of indexes, tables, and databases to detect file corruption.
Supported Database Stacks
- Standalone MariaDB, MySQL, and Percona
- Primary-Secondary Cluster based on MariaDB, MySQL, or Percona
- Primary-Primary Cluster based on MariaDB, MySQL, or Percona
- Galera Cluster based on MariaDB
- XtraDB Cluster based on Percona
The add-on can be installed automatically with a supported database cluster or manually from Marketplace.
Add-On Installation
Open the Marketplace Add-Ons section and select Database Corruption Diagnostic.

In the installation window, provide:
- User and Password — database administrator credentials.
- Environment name — environment containing the required database or cluster.
- Nodes — database layer to diagnose.

Click Install and wait for the success confirmation.
Running Corruption Diagnostics
Open the database layer’s Add-On tab and click Corruption Diagnostic.

Diagnostic Results and Logs
After a few minutes, the platform displays the result in a pop-up notification. For more detail, open:
/var/log/db_recovery.log
Use Show Logs to review the complete diagnostic output.


If Corruption Is Detected
If corrupted data is found, restore the database from a known-good backup. Use the Database Backup/Restore Add-On to schedule recurring backups so a recent recovery point is available.
Expected Result
The selected database or cluster is checked for corruption across indexes, tables, and databases. The result appears in the dashboard and detailed information is available in /var/log/db_recovery.log.
Important Notes
- Supports standalone and clustered MySQL, MariaDB, and Percona topologies.
- Checks indexes, tables, and databases for corruption.
- Database administrator credentials are required for installation.
- The diagnostic temporarily stops database services.
- Detailed output is stored in
/var/log/db_recovery.log. - If corruption is detected, restore from a verified backup.
