[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-03-06。"],[[["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."]]],[]]