Skip to content

binary-log-archiving/binary-log-archiving.org

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

4 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

MySQL Binary Log Archiving & Point-in-Time Recovery (PITR) Automation

MySQL Binary Log Archiving & Point-in-Time Recovery (PITR) Automation

A production-focused, code-first knowledge base for automating MySQL binary log archiving, GTID lifecycle management, and point-in-time recovery.

🌐 Live site · GTID & Architecture · Archiving & Object Storage · PITR Workflows


Why this exists

The binary log is the deterministic execution trace behind MySQL replication and point-in-time recovery. Treating it as a tier-one reliability component — with idempotent automation, strict validation gates, and verifiable archives — is what separates a recovery plan that works from one that fails silently during an incident.

binary-log-archiving.org is a practical, vendor-neutral resource for the engineers who own that reliability: MySQL DBAs, database reliability engineers, and Python automation builders. Every page is engineered around real MySQL 8.0+ behaviour — GTID continuity, binlog_format=ROW determinism, safe retention boundaries, and Python orchestration that streams, compresses, encrypts, and verifies binary logs into durable object storage. Recovery is treated as code: testable, observable, and repeatable.

What you'll find

The knowledge base is organised into three connected areas, each with focused operational guides and deep-dive playbooks:

The server-side foundations: how MySQL serializes events, ROW vs STATEMENT vs MIXED formats, GTID tracking and enforcement, retention boundaries, crash-safe recovery, security and access frameworks, and fallback routing when replication breaks.

The durable-retention pipeline: streaming closed segments to S3/GCS, compression and encryption workflows, rotation scheduling, async queue management, error handling and dead-letter routing, base-backup integration, timestamp targeting, and lifecycle/cost management.

The recovery half, end to end: driving mysqlbinlog replay, scheduled RTO/RPO recovery drills, snapshot & binlog coordination, a Python binlog-parsing library reference, and the validation gates that prove a chain is recoverable before an incident forces it.

Highlights

  • Every guide is code-first — production-grade Python 3.10+ (typed dataclasses, connection pooling, tenacity retries, structured logging) and version-tagged SQL.
  • Hand-authored, accessible diagrams — original inline SVGs that adapt to light and dark themes, no third-party runtime.
  • Deep interlinking — concepts link to their own in-depth guides so you can go as shallow or as deep as you need.
  • Practical comparisons — decision guides such as zstd vs lz4, S3 vs GCS sync pipelines, IAM roles vs Vault dynamic secrets, and mysql-connector-python vs PyMySQL vs python-mysql-replication.
  • 50+ guides spanning fundamentals to expert edge cases, structured so every page is one or two clicks from its topic area.

Built with

  • Eleventy (11ty) — static site generator (Nunjucks + Markdown).
  • Hand-authored inline SVG — original, theme-aware, accessible diagrams.
  • Structured data (JSON-LD)TechArticle, BreadcrumbList, HowTo, and FAQPage on every page.
  • Progressive web app — offline app-shell caching via a service worker.
  • Cloudflare Workers — static-asset hosting at the edge.

Live site

👉 https://www.binary-log-archiving.org

Topics

mysql · binary-log · binlog · point-in-time-recovery · pitr · gtid · database-reliability · disaster-recovery · mysqlbinlog · database-backup · sre

About

MySQL binary log archiving, GTID management, and point-in-time recovery (PITR) automation — a production-focused, code-first knowledge base for DBAs and reliability engineers.

Topics

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

No releases published

Packages

 
 
 

Contributors