<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recovery on Ivan Luminaria</title><link>https://ivanluminaria.com/en/tags/recovery/</link><description>Recent content in Recovery on Ivan Luminaria</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 31 Mar 2026 08:03:00 +0100</lastBuildDate><atom:link href="https://ivanluminaria.com/en/tags/recovery/index.xml" rel="self" type="application/rss+xml"/><item><title>Binary logs in MySQL: what they are, how to manage them, and when you can delete them</title><link>https://ivanluminaria.com/en/posts/mysql/binary-log-mysql/</link><pubDate>Tue, 31 Mar 2026 08:03:00 +0100</pubDate><guid>https://ivanluminaria.com/en/posts/mysql/binary-log-mysql/</guid><description>&lt;p&gt;The message in the infrastructure team&amp;rsquo;s Slack channel was the kind that makes you look up from your screen: &amp;ldquo;Disk at 95% on the production db. Anyone able to look?&amp;rdquo;&lt;/p&gt;
&lt;p&gt;The server was a MySQL 8.0 on Rocky Linux, a business management system used by about a hundred users. The database itself was around 40 GB — nothing extraordinary. But in the data directory there were 180 GB of binary logs. Six months&amp;rsquo; worth of binlogs that nobody had ever thought to manage.&lt;/p&gt;</description></item></channel></rss>