0 views collected around this technical thread.
This article explains why MySQL backups are essential, defines RTO and RPO, compares physical and logical backup methods, describes snapshot, binary‑log, incremental and differential strategies, and provides best‑practice recommendations and example commands for reliable backup and recovery.
This article explains the principles of disaster recovery for MySQL, covering RTO/RPO metrics, national backup level standards, common master‑slave topologies, a comparative analysis of high‑availability solutions, and a detailed three‑center multi‑region replication design with code patches to avoid replication loops.
This article explains the core concepts of data replication, backup strategies, and disaster recovery, covering RTO/RPO metrics, backup types, copy data management, and the differences between data‑level, application‑level, and business‑level disaster recovery solutions.
This article explains the core concepts of disaster recovery and data backup—including RTO, RPO, recovery levels, cloud disaster recovery, backup types, copy data management, deduplication, compression, and block/file/database backup—while also noting related commercial offerings.
The OceanBase 4.0 core technology presentation recounts twelve years of evolution from the early 0.1 version to a single-node distributed integrated database, highlighting breakthroughs such as sub-8-second RTO, RPO = 0, Paxos three-replica high availability, and competitive performance in TPC-C and TPC-H benchmarks.
This article provides a comprehensive overview of disaster recovery, covering its definition, the distinction between backup and DR, their respective roles, key metrics such as RPO and RTO, various replication technologies, and practical implementation methods across storage, network, and host layers.
This article explains why database backup is essential, outlines multi‑region and multi‑media deployment requirements, compares physical and logical backup methods, reviews MySQL backup tools, shows performance differences, and provides practical guidance on verifying backup integrity and minimizing RTO and RPO.
The article explains Haro’s approach to system stability—defining high‑availability, key metrics such as SLA, RPO/RTO, MTTR/MTBF, and the 5‑5‑10 rule—while outlining cultural and technical safeguards, full‑team participation, process integration, and incremental tooling to prevent faults and ensure rapid recovery.
This article provides a detailed introduction to disaster recovery, covering backup concepts, continuous data protection, high‑availability and disaster‑recovery architectures, key metrics such as RTO and RPO, and the three levels of disaster‑recovery solutions from data to business continuity.
This article explains disaster tolerance, fault tolerance, and disaster recovery, compares them with backup, discusses RTO/RPO metrics, outlines disaster types, and presents common disaster‑recovery architectures and planning considerations for enterprise IT operations.
This article explains the definitions of disaster tolerance, fault tolerance, and disaster recovery, compares their purposes, discusses backup versus disaster‑tolerance solutions, outlines key metrics such as RTO and RPO, and presents common architectural and investment considerations for building resilient enterprise systems.
The talk by Tencent’s senior MySQL engineer explains high‑availability concepts—99.95% uptime, RPO/RTO metrics, backup methods, and replication modes—while comparing single‑node, shared‑storage, and share‑nothing architectures, detailing failover tools (Keepalived, MMM, MHA), cluster solutions (PXC, MGC, Group Replication) and NewSQL examples such as Aurora, PolarDB and CynosDB.
The article explains what constitutes a fault, introduces key metrics such as RPO and RTO, and describes various fault isolation principles, patterns, and practical examples—including dependency degradation, failover, dynamic adjustment, fast‑fail, caching, rate limiting, and resource isolation—to improve system reliability.