https://ivanluminaria.com/en/tags/restore/Recent content in Restore on Ivan LuminariaHugoenTue, 14 Apr 2026 08:03:00 +0100https://ivanluminaria.com/en/posts/mysql/mysqldump-mysqlpump-mydumper/Tue, 14 Apr 2026 08:03:00 +0100https://ivanluminaria.com/en/posts/mysql/mysqldump-mysqlpump-mydumper/<p>The call came on a Friday afternoon — because these things always happen on Fridays. The DBA from a logistics client messages me on Teams: &ldquo;Last night&rsquo;s backup took three and a half hours. This morning users found the application sluggish at 8 AM. Can we talk?&rdquo;</p> <p>We could talk. In fact, we should have talked about this a while ago.</p> <p>The setup was a classic: MySQL 8.0 on Rocky Linux, roughly 60 GB database, a business application with about thirty InnoDB tables, four or five of which were truly large — the orders table, the warehouse movements table, the tracking history. The backup ran every night via a mysqldump launched by cron at 2:00 AM. It had worked for years. The problem was that the database had grown in the meantime.</p>