{"id":26067,"date":"2025-03-26T12:35:36","date_gmt":"2025-03-26T19:35:36","guid":{"rendered":"https:\/\/www.pingcap.com\/?p=26067"},"modified":"2025-03-29T04:36:41","modified_gmt":"2025-03-29T11:36:41","slug":"optimizing-backup-verification-enhancing-performance-reliability-tidb","status":"publish","type":"post","link":"https:\/\/www.pingcap.com\/ko\/blog\/optimizing-backup-verification-enhancing-performance-reliability-tidb\/","title":{"rendered":"Optimizing Backup Verification: How to Enhance Performance and Reliability in TiDB"},"content":{"rendered":"

With the release of TiDB 8.5, TiDB BR (Backup & Restore)<\/a> has made a significant change: Full-table checksum verification is now turned off by default during backups. This update boosts backup efficiency by cutting unnecessary overhead while keeping data integrity intact.<\/p>\n\n\n\n

In this post, we’ll explain how \ud2f0DB<\/a> has optimized backup verification, the expected performance benefits, and why full-table checksums might no longer be essential for most users.<\/p>\n\n\n\n

<\/span>A Smarter Approach to Backup Verification<\/span><\/h2>\n\n\n\n

Previously, TiDB BR’s checksum process involved two full-table scans:<\/p>\n\n\n\n

    \n
  1. The first scan during backup to extract data and compute checksums.<\/li>\n\n\n\n
  2. A second scan, via coprocessor requests, to validate the backup’s integrity.<\/li>\n<\/ol>\n\n\n\n

    While effective, this method added significant performance costs, especially with large datasets. Each backup essentially doubled the I\/O workload, leading to longer backup times and higher resource use.<\/p>\n\n\n\n

    Real-world experience shows that such rigorous checks are often unnecessary. Instead of relying on intensive full-table scans, TiDB BR now uses more efficient validation techniques that ensure reliability without extra performance costs.<\/p>\n\n\n\n

    <\/span>Maintaining Backup Integrity<\/span><\/h2>\n\n\n\n

    Turning off full-table checksums by default doesn\u2019t compromise backup integrity. TiDB BR includes multiple safeguards:<\/p>\n\n\n\n