1 views collected around this technical thread.
This guide explains how to use mysqldump to back up a single MySQL database, multiple databases, or all databases, includes options for specific tables, compression with gzip, adding drop statements, exporting only schema, and provides restore procedures and a sample automated backup script.
This article compiles real‑world operations incidents—from accidental database deletions and faulty deployments to hidden data tampering and network device failures—highlighting how quick diagnosis, preventive maintenance, and SRE practices can mitigate impact on users, reputation, and revenue.
This article provides step-by-step Bash scripts for automating daily MySQL database backups, compressing tables, cleaning old archives, and configuring master‑master replication, including detailed commands for dumping databases, creating tar.gz packages, and setting up replication parameters on Linux servers.
The article explains how to respond to accidental MySQL data deletion by analyzing loss causes, choosing recovery methods such as mysqldump backups, binary‑log point‑in‑time restores, or Percona’s InnoDB tool, provides step‑by‑step commands, and recommends preventive practices like regular backups, transactions, and strict permissions.
This article explains the new mysqld-long-query-time option added to MySQL 8.0.30's mysqldump tool, shows how to configure it, presents comparative experiments demonstrating its effect on slow‑query logs, and provides conclusions and additional notes for practical database backup scenarios.
Vivo replaced its fragile Python‑Celery backup system on GlusterFS—characterized by two‑day MySQL backups, single‑point failures, and weak security—with a Java‑based architecture using a Redis cluster and object storage, adding automated copying, verification, point‑in‑time recovery and migration, cutting backup windows to about ten hours and achieving near‑100 % success.
This article presents a comprehensive analysis of the shortcomings of an existing database backup solution and details the architecture, high‑performance backup and restore mechanisms, dynamic throttling, storage abstraction, and experimental results of a newly designed, scalable backup‑recovery platform for MySQL databases.
This article explains how to use Python to automatically back up SQL databases by installing required packages, establishing a connection with pyodbc, executing backup commands, recording backup details with pandas, and scheduling the script for regular execution, providing code examples for each step.
This guide explains how to prepare the environment, install required dependencies and a newer GCC toolset, and then compile, build, and install Percona XtraBackup 8.0 from source on an Aarch64 Kylin v10 system, including troubleshooting tips for common issues.
Easy Dump is a Bash‑based utility that streamlines PostgreSQL backups by wrapping pg_dump and pg_dumpall, offering multiple dump modes, parallel execution, table exclusion, automatic configuration generation, and detailed success or failure notifications for reliable database migration and maintenance.
The article investigates a bug introduced in MySQL 5.7.36 where mysqldump writes the SET @@GLOBAL.GTID_PURGED statement at the end of the dump file, causing GTID and data inconsistencies that break replication, and recommends using an older mysqldump version until the issue is fixed.
This article recounts a real-world incident where a client mistakenly imported 60,000 rows of erroneous Excel data into a MySQL production database, leading to an accidental bulk delete, and explains how the team used MySQL binlog to recover the lost data while offering practical safeguards to prevent similar disasters.
The article investigates the MySQL 5.7 sys schema ERROR 1356 caused by mysqldump --all-databases dropping mysql.proc, explains why the bug occurs, cites official documentation and bug reports, and provides four practical solutions including mysql_upgrade, separate sys backups, using --databases, and rebuilding from mysql‑sys.
The MySQL Clone Plugin, added in 8.0.17, enables fast local or remote cloning of InnoDB data by installing the plugin, issuing CLONE commands, monitoring progress via performance_schema tables, and using the resulting GTID or binlog coordinates to build replicas, while observing limitations such as DDL restrictions and single‑instance operation, and offering advantages over XtraBackup through an extra page‑copy stage and simplified GTID handling.
The article explains how MySQL multi‑source replication can be employed to back up, horizontally or vertically partition, and merge data from several servers into a single target database, illustrating three typical scenarios and providing example SQL for data consolidation.
This article explains how mysqldump’s --net-buffer-length option can be used to split INSERT statements into manageable batches, defines large transactions, shows performance testing with different buffer sizes, and concludes that the default settings already avoid large transactions and provide acceptable import performance.
After costly data‑deletion mishaps, 37 Interactive Entertainment engineered a robust, multi‑region backup platform that evolved from simple cron scripts to streaming xtrabackup with Celery‑driven task queues, encrypted HDFS/S3 storage, automated rotation and restore verification, ensuring reliable protection against high‑impact data loss.
This tutorial explains how to use Navicat to back up a test database, delete and restore product data, and synchronize schema changes between test and production databases, providing detailed step‑by‑step instructions with screenshots.
This article explains a comprehensive database backup workflow—including daily full backups with xtrabackup, real‑time binlog incremental backups, multi‑level retention policies, automated failure detection, disaster‑recovery across multiple data centers, and fast table‑level restoration—to help prevent prolonged outages.
This article examines the Hearthstone database rollback incident, highlighting the timeline, power‑related hardware failures, backup shortcomings, and offers concrete MySQL backup and server‑monitoring recommendations to prevent similar data loss in game operations.