[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間:2025-06-16 (世界標準時間)。"],[[["Backup and DR protects MySQL databases in Linux environments using both volume-level backups with Linux change block tracking (CBT) and LVM snapshots, and file-based backups via the `mysqldump` API."],["Volume-level backups utilize MySQL APIs to freeze and unfreeze the database, create LVM snapshots, track changed blocks with CBT, and copy only changed blocks to the backup/recovery appliance."],["File-based backups use the `mysqldump` API to write full backups to a mounted staging disk, and log backups are performed directly from the file-system."],["For recovery, Backup and DR mounts a rewritable staging disk and brings the database online instantly in the volume-level method, and in the file-based method, it mounts the staging disk and restores the database, with logs being able to be played to any point in time after restoration."],["MySQL binary logs can be purged via the `purge binary logs before` API during a log backup, which also copies all the binary logs."]]],[]]