0 views collected around this technical thread.
This article explains WeChat’s hidden “recover” feature, detailing its official purpose, technical limits, step‑by‑step recovery methods, effectiveness, backup strategies, and the risks of third‑party tools, helping users safely restore lost chat records.
The article explains how Baidu Cloud Redis's Data Flashback feature combines RDB snapshots with timestamped AOF logs to provide fast, space‑efficient, point‑in‑time data recovery, overcoming the limitations of native Redis persistence in high‑traffic scenarios.
This article explains how to use MySQL flashback utilities such as binlog2sql, my2sql, and MyFlash to recover from accidental DML operations, covering supported SQL types, required binlog settings, tool features, command‑line usage examples, and best‑practice recommendations for preventing future data loss.
This article explains how MySQL redo logs and binlog logs work together to ensure data durability, consistency, and high availability, covering InnoDB crash‑recovery, flush policies, log file groups, binlog formats, two‑phase commit, and the complete recovery workflow.
To recover accidentally deleted MySQL rows, ensure binary logging is enabled and set to ROW mode, locate the appropriate binlog files, use mysqlbinlog (or tools like binlog2sql) to extract the original INSERT events within a time window, and replay or reconstruct them to restore the data.
This guide explains how to prevent data loss in MySQL by enabling backups and binlog, performing full restores with mysqldump or xtrabackup, executing point‑in‑time recovery, restoring individual tables, skipping erroneous SQL statements, and using flashback tools like binlog2sql and MyFlash.
After a junior engineer mistakenly ran an unguarded rm -rf command that wiped an entire production server—including MySQL and Tomcat—I documented the step‑by‑step recovery using ext3grep, extundelete, and MySQL binlog, highlighting the lessons learned for future operations.
This guide walks through recovering a deleted MySQL database stored in Docker volumes by locating the mysql.ibd file, recreating a container with the same image, and mounting the original volume, allowing the lost data to be restored without a backup.
This article details a step‑by‑step recovery of a ClickHouse 4‑shard, 3‑replica cluster after a node’s disks failed, covering verification of residual data, Zookeeper metadata cleanup, table reconstruction, distributed table restoration, and validation of synchronization across replicas.
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 guide explains how to answer MySQL accidental deletion interview questions and outlines practical recovery methods—including backup restoration, binlog usage, third‑party tools—and essential preventive practices such as regular backups, transaction handling, and permission management.
This guide walks through locating the Docker volume of a removed MySQL container, creating a new container with the same image, and swapping the volumes to restore the original database, providing step‑by‑step commands and screenshots for successful data recovery.
This article explains Redis AOF persistence, covering how the Append‑Only File logs write commands, the configuration options for enabling and syncing AOF, the rewrite process that compresses the log, and how AOF compares with RDB snapshots and hybrid persistence for reliable data recovery.
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 tutorial demonstrates how to use PHP to create a backup directory, export MySQL tables to text files, and restore them by reading the files and executing INSERT statements, providing complete code examples for both backup and recovery processes.
This article explains how Redis ensures data durability by using two persistence strategies—Append Only File (AOF) and Redis Database (RDB) snapshots—detailing their operation, configuration options, trade‑offs, rewrite processes, and how they handle expired keys and recovery.
This article provides an in‑depth overview of MySQL backup classifications—including hot, warm, and cold backups—explains physical versus logical backup methods, compares built‑in and third‑party tools such as mysqldump, mysqlhotcopy, LVM snapshots, XtraBackup, and presents step‑by‑step command examples for each approach.
This guide explains how to restore a mistakenly dropped MySQL table by enabling binlog, creating backups, extracting relevant statements from the binlog, editing out DROP commands, and re‑importing the data to recover the table to its state before deletion.
This article explains how to prevent data loss in MySQL by enabling binlog in ROW format, performing full and incremental restores using mysqldump or XtraBackup, executing point‑in‑time recovery, restoring individual tables, skipping erroneous SQL statements, and using flashback tools such as binlog2sql and MyFlash.
This guide explains why careful file deletion matters, introduces Linux tools like lsof and extundelete for recovering mistakenly removed files, and provides step‑by‑step commands, installation instructions, and precautions to maximize recovery success while avoiding data loss.