The server is on a version nobody supports
A MariaDB 10.3 or 10.4 install that has been running since it was installed by cPanel or a hosting template, with no security fixes arriving any more.
Upgraded to a current release
Working with MariaDB?
Most MariaDB servers that reach us were installed as the default database by some other piece of software and then left alone for years. We work out exactly which version is running, what it is incompatible with, and what it will take to bring it forward without losing a byte.
What it is
MariaDB is an open-source fork of MySQL that was started in 2009 by Monty Widenius, the original author of MySQL, after Oracle acquired Sun (and MySQL with it). It is developed today by the MariaDB Foundation and the MariaDB Corporation, and it is the default MySQL replacement on many Linux distributions including Debian, Red Hat and Fedora, as well as most cPanel hosting installs.
Beyond being a drop-in for MySQL, MariaDB adds its own storage engines such as Aria and ColumnStore, built-in Galera multi-master clustering, and various extensions to SQL. The 10.x branches are the long-term stable line that most production deployments still run, while MariaDB 11.x is the current release series.
The honest version
No technology is all upside. This is where MariaDB earns its place and where it tends to cause trouble.
Sound familiar?
The MariaDB problems that bring people to us, and what you have once each one is fixed.
A MariaDB 10.3 or 10.4 install that has been running since it was installed by cPanel or a hosting template, with no security fixes arriving any more.
Upgraded to a current release
Dumps produced by a recent MariaDB include syntax and options that MySQL refuses to import, and the application now depends on behaviour that differs between them.
A clean, portable export
One cluster member is falling behind, usually because of a long-running query, a schema change applied the wrong way, or network jitter between availability zones.
Cluster stable under write load
A single-threaded replica that cannot keep up with a busy primary, or a workload full of large transactions that serialise on the replica.
Replica keeping up in real time
Statistics that have gone stale after bulk loads, indexes that no longer match how the app reads, or buffer pool sized for a much smaller database.
Measured, indexed, tuned
Nightly mysqldump files that nobody has restored, or Mariabackup output sitting on the same server it would need to rescue.
Off-server backups with tested restores
No documentation, root passwords in a text file, and a mix of application accounts with privileges nobody can explain.
Access and inventory back in your hands
What we do
Call us for one stuck upgrade, or hand us the whole fleet.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
It depends on which features the application uses and which release of each you are comparing. For a basic LAMP site either works; for anything using JSON functions, CTEs, authentication plugins or specific replication features, we test the application against both and tell you plainly which is the better fit.
Yes. Those versions are past end of life and no longer get security fixes. We rehearse the upgrade on a copy of your data first, run mariadb-upgrade, test the application against the new release, and only then schedule the real cutover.
Yes, and we will also be honest about whether you actually need one. Galera brings synchronous multi-master writes and real high availability, at the cost of operational discipline. For many workloads a primary with a read replica is a better fit.
Usually it is a single-threaded replica trying to keep up with a multi-threaded primary, a workload dominated by long transactions, or disk on the replica that is slower than on the primary. Parallel replication, binlog format changes and hardware changes are the common fixes.
Yes. We inventory the servers, document the versions, replication topology and accounts, rotate credentials, and put monitoring and backups in place before anything else.
Estimates are free. Describe the version, the hosting and the problem and you get a price before any work begins.
Free estimate
Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: