This article explains how InnoDB's redo log works as a safety cushion, detailing its generation, buffering, flushing, circular storage, and recovery process to ensure transaction durability even when the database crashes unexpectedly.
This article explains why MySQL data pages can suffer partial write failures during crashes, how the mismatch between InnoDB and OS page sizes contributes to the problem, and how the Double Write Buffer mechanism safeguards data integrity by providing a recoverable copy of each page.
This article provides a step‑by‑step tutorial for DBAs to design a reliable MySQL backup strategy, write a Bash automation script, schedule it with cron, and perform restoration drills using Docker containers, while covering directory planning, command checks, cleanup, and common troubleshooting.
This guide explains how to diagnose and fix a PostgreSQL instance that fails to start after a power outage, covering log inspection, missing socket files, PID checks, checkpoint corruption detection, and recovery using pg_resetwal.
This article presents two real‑world MySQL recovery scenarios—full backup restoration after an accidental table deletion and incremental recovery using XtraBackup—detailing backup strategies, binlog extraction, step‑by‑step commands, and validation procedures to safely restore production databases.
Explore 15 classic MySQL log interview questions covering redo log, WAL, binlog, undo log, two‑phase commit, write‑ahead logging, crash‑safe mechanisms, log flushing settings, and recovery procedures, with detailed explanations, execution flow diagrams, and configuration parameters to help you ace database engineering interviews.
This article compiles 15 classic MySQL log interview questions and provides detailed explanations of redo log, WAL, binlog, undo log, two‑phase commit, crash‑safe mechanisms, and related configuration parameters, helping readers understand database recovery and replication fundamentals.
After a power outage caused a PostgreSQL instance running in Kubernetes to fail with connection errors and an invalid primary checkpoint record, this guide explains how to diagnose missing socket files, inspect process IDs, use pg_resetwal to repair the checkpoint, and successfully restart the database.
This article presents 15 classic MySQL log interview questions and provides detailed explanations of redo log, WAL, binlog, undo log, two‑phase commit, log flushing mechanisms, and recovery strategies, helping readers deepen their database knowledge and ace technical interviews.
An in‑depth guide explains MySQL’s write‑ahead log mechanism, covering buffer pool, redo and undo logs, checkpoint types, and how the system recovers from power failures, with step‑by‑step examples and practical configuration tips for reliable data consistency.
This article explains MySQL InnoDB’s write‑ahead logging, detailing the roles of Buffer Pool, Redo and Undo logs, checkpoint mechanisms, and how they ensure data consistency and atomicity when a sudden power loss occurs.
This guide explains how to rescue both physically and logically deleted Oracle databases, covering RMAN file recovery, full database restoration, flashback table techniques, recycle‑bin usage, flashback database configuration, and essential backup strategies to prevent data loss.
This article explains MySQL's fault‑tolerance mechanisms, covering data persistence, storage engines, the binary, redo, and undo logs, WAL, two‑phase commit, and step‑by‑step recovery procedures for accidental data loss or crashes.
This article analyzes a MongoDB replication failure caused by missing oplog entries, compares logical initialization repair methods with Redis replication, and provides practical steps—including oplog size adjustment and snapshot techniques—to restore synchronization and prevent similar issues in production environments.
This article describes how to identify, analyze, and fix InnoDB page corruption in MySQL instances, covering log inspection, querying metadata tables, using innodb_force_recovery, and the inno_space tool, with example commands and best‑practice recommendations to prevent data loss.
This guide explains how to use the OceanBase server_permanent_offline_time parameter to permanently offline a faulty node, rebuild its data, and restore normal operation, including preparation, command steps, verification, and recommended settings for production.
This article explains how to simulate and diagnose segment failures in a Greenplum cluster, including identifying master, segment, and tablespace issues, generating recovery configuration files, and using gprecoverseg and gpstate commands to restore segment roles and ensure all nodes are operational.
This article explains how MySQL 8.0's InnoDB generates Redo logs, groups them into mini‑transactions, writes them concurrently to the log buffer, and uses log_writer and log_flusher threads together with LSN, slots, and recent_written structures to ensure durable, ordered persistence.
This article explains MySQL's redo log, binlog, and undo log, covering their roles in crash recovery, durability, performance optimization, log formats, two‑phase commit handling, and how they together ensure data consistency and atomicity in InnoDB.
This article explains how a deep understanding of database internals, illustrated by an Oracle recovery story, enables you to restore PostgreSQL instances when WAL files or pg_control are missing, providing detailed command parameters, preparation steps, and cautions for safe recovery.
This article explains the implementation principles, design ideas, and source‑code analysis of PostgreSQL's pg_recovery tool, detailing how it reads dead tuples, controls memory, and returns data through a custom function with configurable parameters.
This guide walks through exporting business databases, re‑initializing the MySQL instance, importing data, extracting GTID information, creating replication and monitoring accounts with helper functions, resetting logs, and finally re‑joining the node to a MySQL Group Replication cluster.
This article explains why Redis RDB snapshots are ideal for enterprise cold backups, provides step‑by‑step Linux scripts and cron jobs for hourly and daily backup retention, and details the complete restoration process from saved RDB files.
This guide walks through restoring a mistakenly updated Oracle 11.2.0.1 table to a specific point in time using RMAN tablespace recovery on a new host, handling Windows-specific issues, and finally retrieving the data via a database link, with full scripts and step‑by‑step instructions.
This article explains the principles of Logical Undo Logging, compares it with Physical Logging, and examines advanced recovery techniques such as SQL Server's Constant Time Recovery and the in‑memory database Silo's Force Recovery, highlighting their impact on concurrency, performance, and recovery latency.
This guide walks through simulating corruption of Oracle password, parameter, control, data, and log files, demonstrates the resulting errors, and provides step‑by‑step RMAN and SQL commands to restore each file type while emphasizing backup best practices.
On Feb 23, Weimeng suffered a large‑scale system outage caused by a core operations staff mistakenly deleting production databases, prompting a multi‑day recovery effort with Tencent Cloud support; the article examines the incident’s background, historical parallels, crisis response, and broader operational insights for DevOps and reliability engineering.
The article analyzes the recent Weimob data‑deletion incident, explaining why recovery is complex, comparing on‑premise, hybrid, and full‑cloud database architectures, and outlining the technical steps and obstacles involved in restoring massive lost data.
After a core operations staff accidentally deleted Weimeng’s production database in February, the platform endured a multi‑day outage, prompting a transparent crisis response, extensive Tencent Cloud support, and a deep analysis of recovery challenges, operational best practices, and the broader lessons for modern DevOps teams.
This article explains how InnoDB uses REDO logs to recover a crashed MySQL database, detailing the steps of locating checkpoints, scanning log segments, parsing mini‑transactions, storing records in hash tables, and applying them to restore data consistency.
MySQL Flashback leverages the ROW‑format binary log to generate inverse DML statements—turning deletes into inserts, updates into reverse updates, and inserts into deletes—while tools parse WriteRows, UpdateRows, and DeleteRows events, using injected Pseudo GTID markers to delimit change ranges and enable automated rollback despite DDL limitations.
This article explains MySQL binlog’s role, surveys existing flashback implementations, and details NetEase’s custom patch that adds flashback support by parsing and reversing binlog events, including event types, code logic, and comparisons with MariaDB, Oracle, and TiDB solutions.
This article walks through diagnosing a MySQL crash, using innodb_force_recovery to start the server, exporting the data with mysqldump, handling charset mismatches, importing into a new instance, and restoring normal operation while offering best‑practice backup recommendations.
When a SQL Server database crashes and you lack recent backups or usable transaction logs, you can still attempt recovery by attaching the data file, switching the database to emergency mode, running DBCC checks, and rebuilding objects, though some data loss may be inevitable.
Xtrabackup is an open-source hot backup tool for InnoDB and XtraDB databases, offering non-blocking backups with features like fast backup speeds, reliable physical backups, and efficient disk space usage. The recovery process involves complex log parsing and page flushing mechanisms, which can be optimized to improve performance, especially for large datasets.
This guide walks through stopping services, backing up the MySQL data directory, compiling the undrop‑for‑InnoDB tool, parsing ibdata1 to rebuild system tables, extracting CREATE TABLE statements, and loading recovered data back into MySQL, while highlighting common pitfalls such as command‑line flags and UTF‑8 emoji issues.
The article details a step‑by‑step recovery of an Oracle database where the SYSAUX01.DBF file was corrupted, using DBV detection, attempted repairs, analysis of export/Data Pump failures, and low‑level file parsing to fully restore the ZXFG user's data.
After a disastrous ERP data loss caused by a careless drop, this article walks through the importance of backups and provides a detailed, practical MySQL recovery process using full backups, binlog extraction, and incremental restoration to retrieve lost tables.
This guide explains how to restore an accidentally dropped MySQL database by leveraging nightly full backups and incremental binlog files, detailing the required configuration, command usage, and step‑by‑step procedures to safely recover lost data.
WeChat’s WCDB component tackles pervasive SQLite corruption on mobile devices by combining dump‑based, backup, and B‑tree parsing recovery methods, achieving up to 78% success while supporting encrypted databases, large data volumes, and seamless user experience.
This guide walks through the most common MySQL backup methods—including mysqldump, mysqlbackup, mysqlhotcopy, and Percona XtraBackup—detailing command syntax, options, lock behavior, restoration steps, and practical examples for both logical and physical backups.
This guide explains how to use Percona XtraBackup for fast single‑table recovery in both local full‑backup and remote streaming scenarios, detailing preparation steps, command examples, and essential configuration tweaks to minimize downtime and data loss.
This comprehensive guide explains Oracle database failure types, the DBA's role in ensuring availability, and detailed recovery techniques—including flashback, instance recovery, checkpoint handling, redo log management, and configuration of fast recovery areas—to minimize downtime and data loss.
This article explains Oracle Flashback technology—from basic flashback queries and version queries to transaction-level recovery—detailing required undo tablespace settings, essential parameters, SQL syntax, and step‑by‑step examples that demonstrate how to restore erroneous DML operations efficiently.
This guide walks through simulating a catastrophic Oracle database failure, performing incremental RMAN backups, verifying backup completeness, and executing a full restore and recovery—including spfile, controlfile, datafiles, and archived logs—so you can confidently recover a database after total data loss.
Understanding InnoDB log files is crucial for MySQL recovery and performance; this guide explains their role, the impact of size on checkpoints and recovery time, and provides a step‑by‑step method to calculate an optimal log size based on one hour of generated logs.
This article walks through a real Oracle 11gR2 datafile loss case, explains how backup‑software snapshots caused mismatched SCNs, and details step‑by‑step recovery methods—including offline drop, header SCN editing, and forcing the database open with SCN adjustment—to successfully restore the instance.
This guide explains why ORA-38706 and ORA-38707 occur when Flashback Database is turned on, shows how to switch the Oracle database to ARCHIVE mode, and provides step‑by‑step SQL commands to enable Flashback and verify the configuration.
When an Exadata diskgroup fails to mount, this article walks through using AMDU to extract control, data, and log files, handling OMF and custom formats, advancing SCN, and finally opening the database, while also recommending preventive tools and regular maintenance.
A step‑by‑step guide shows how to reinstall Oracle 11g, adjust environment variables, copy essential files, recreate Oracle services, and verify the database connection to restore a Windows‑based Oracle database that was damaged by antivirus deletions.
This article explains Oracle's undo mechanism, detailing how it enables consistent reads, supports transaction rollback, and facilitates instance recovery by tracking SCN numbers and chaining undo blocks to reconstruct past data states.
The article explains why Oracle bad block incidents demand scenario‑driven handling, outlines interview questions, describes the pitfalls of inspecting each alert log, and advocates promptly switching to disaster‑recovery and using backups to restore service, while sharing real‑world cases and practical DBA advice.
This article walks through two unconventional Oracle recovery techniques—restoring a mistakenly deleted datafile by leveraging Linux file descriptors and bypassing a missing archive log with BBED—detailing the scenarios, analysis, step‑by‑step commands, and practical considerations.
This guide introduces the free gDUL 3.0 tool for Oracle DBAs, detailing its export capabilities, directory layout, configurable parameters, platform‑specific setup tips, and step‑by‑step usage to recover data from inaccessible databases.
