Why You Should Upgrade MySQL or MariaDB and How to Perform a Safe Upgrade

1. Why You Must Upgrade MySQL or MariaDB

For security, support, and compatibility reasons, it is strongly recommended to always upgrade to the latest stable version of MySQL or MariaDB. cPanel & WHM enforces strict upgrade policies to protect your server.

Upgrade blocks may occur due to:

• Higher RAM requirements in newer versions
• Removal of deprecated features
• Incompatibility with outdated software

If you stay on an outdated version, you risk:

• Running unsupported and insecure database software
• Compatibility issues with WordPress, plugins, and third‑party apps
• Losing access to new cPanel features
• Exposure to unpatched vulnerabilities (e.g., the major Exim issue in 2019)

Golden Rule: Upgrade as soon as possible to avoid sudden database failures or compatibility issues.

2. Steps to Upgrade MySQL or MariaDB

Step 1 — Check Application Compatibility

Ensure all applications (WordPress, Joomla, custom scripts, etc.) support the new MySQL version.

Step 2 — Plan a Maintenance Window

Notify users that websites may temporarily go offline during the upgrade.

Step 3 — Create a Full Backup

Use WHM:

WHM » Backup » Backup Configuration

Or via CLI:

/usr/local/cpanel/bin/backup

Step 4 — Perform the Upgrade

Recommended Method (WHM 120+)

WHM » Home » Database Services » Upgrade Database Version

Older WHM Versions

WHM » Home » SQL Services » MySQL/MariaDB Upgrade

API Method

Use WHM API 1:

start_background_mysql_upgrade

Command Line Method

/scripts/mysqlup

Step 5 — Test After Upgrade

• Check all websites
• Test applications and plugins
• Verify database‑driven services

If issues occur, hire a professional admin or open a support ticket.

3. Frequently Asked Questions

1. What is Strict Mode and why does it cause warnings?

Strict Mode forces MySQL to reject invalid or incomplete INSERT or UPDATE queries. Older scripts may break, but modern WordPress versions fully support it.

2. Should I check all boxes in Step 2 of the upgrade?

Yes — all boxes must be checked for the upgrade to proceed.

3. Interactive vs Unattended upgrade?

• Interactive: Best for experienced DB admins.
• Unattended: Best for beginners or automated environments.

4. How do I upgrade on a Remote MySQL server?

• If the remote server also runs cPanel → use Upgrade Database Version on that server.
• If it runs another platform → follow that platform’s documentation.

5. How does multi‑step upgrading work?

The system automatically upgrades step‑by‑step. You do not need to manually upgrade to intermediate versions.

6. What services are affected during upgrade?

Component	Affected?	Description
Website appearance	No	Unless incompatible software is used.
Email / Exim	No	Independent from MySQL.
Files	No	Upgrade does not touch files.
Database data	No*	*Unless deprecated SQL syntax is used.
cPanel accounts	No	Accounts remain intact.
Website downtime	Yes	MySQL restarts during upgrade.
Service restarts	Yes	MySQL temporarily stops.

7. How long can I stay on MySQL 5.5 or 5.6?

In cPanel 132+, upgrades are blocked. Staying on old versions removes support and security — strongly discouraged.

8. Should I switch from MySQL 5.5 to MariaDB?

MariaDB differs significantly from MySQL 5.7+. If your software supports these changes, MariaDB offers better performance. But migrating back to MySQL is not supported.

9. Where is the upgrade log?

/var/cpanel/logs/mysql_upgrade_log.YYYYMMDD-hhmmss

Conclusion

Upgrading MySQL or MariaDB is essential for security, performance, and compatibility. By following proper backup, upgrade, and testing procedures, you ensure a smooth transition and prevent unexpected failures.