Overview
MySQL 8.0 moved to Oracle Sustaining Support on 21 April 2026, and a small platform team that already struggles to keep up with on-call, backups and replica health has one more project to schedule. This scenario describes how AceMQ's Tier 3 managed MySQL absorbs both, in an account the customer owns.
Challenge
The team ran its customer-facing database as a source and two replicas on EC2 instances. Backups had never been restored, replica lag grew during the nightly batch, minor releases slipped, and the move to 8.4 LTS kept losing to product work. Older application connectors still authenticated with mysql_native_password, which 8.4 disables by default.
Environment
MySQL 8.0 on Linux EC2 instances in the customer's AWS account, GTID-based asynchronous replication to two replicas, backups to object storage, and a change process the customer's security team controls.
Approach
Onboarding starts with an assessment of release level, backup and binary log retention, replica lag against the batch window, errant GTIDs, client connectors and authentication plugins. Active risks are fixed first. AceMQ then takes the pager under the contracted SLA, working through the customer's access controls and change process, and runs the 8.0 to 8.4 LTS upgrade as a project: rehearsal on a restored copy, a rollback plan at each step and a cutover window agreed with the customer.
Solution
- Assess the release, backup chain, binary log retention, replica lag, errant GTIDs and every client's authentication plugin before taking over
- Set up monitoring for lag, connections, long transactions, deadlocks and disk, routed to AceMQ's on-call
- Schedule restore tests into a scratch environment, with point-in-time recovery tried against a chosen moment, and record the results
- Rehearse the 8.0 to 8.4 LTS upgrade on a restored copy, including the authentication changes and replica apply behaviour
- Keep failover, restore and upgrade runbooks as the customer's property for a clean handover
Outcome
The engagement delivers an assessed estate, active risks remediated, monitoring and on-call run by AceMQ, scheduled restore tests with recorded results, and a rehearsed upgrade to a supported LTS series. The customer's data and AWS account stay with the customer throughout.