Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
MySQL adalah database open source yang paling populer di dunia, yang digunakan oleh properti web
berprofil tinggi.
Halaman ini menjelaskan cara melindungi data database aplikasi MySQL yang konsisten dengan Pencadangan dan DR di lingkungan Linux.
API pencadangan MySQL yang digunakan oleh Cadangan dan DR
Pencadangan tingkat volume (Linux change block tracking dan snapshot LVM): MySQL Flush tables overwriting the data area. With read lock dan Unlock tables API.
Pencadangan Full+Incremental (tradisional berbasis file): MySQL mysqldump
API. Tindakan ini akan menyediakan cadangan database lengkap dalam format cadangan. Saat pemulihan, restore db API memulihkan database dengan menimpa area data secara fisik.
Pencadangan log MySQL: Selama pencadangan log, Pencadangan dan DR secara fisik menyalin
semua log biner MySQL. MySQL purge binary logs before API digunakan
untuk menghapus log biner.
Cara kerjanya: Pencadangan berbasis volume Backup and DR dengan CBT Linux
Hanya blok yang diubah yang dilacak dalam bitmap: tidak ada operasi copy-on-write, tidak ada operasi yang intensif I/O.
Pencadangan dan pemulihan data mengikuti langkah-langkah berikut:
Agen Pencadangan dan DR memiliki CBT untuk melacak blok yang diubah di area data database.
Agen memanggil API database untuk membekukan atau menjeda database untuk pencadangan data.
Agen membuat snapshot LVM area data database dan menyintesis bitmap.
Panggilan agen ke API database untuk mencairkan database.
Agen menyalin blok yang diubah ke appliance pencadangan/pemulihan, yang kemudian menghapus
snapshot dan membuat katalog pencadangan.
Appliance ini mengeluarkan snapshot internal dan menyintesis pencadangan penuh virtual
point-in-time.
Untuk pemulihan data, Pencadangan dan DR langsung memasang disk staging yang dapat ditulis ulang
dan mengaktifkan database secara online.
Cara kerjanya: pencadangan berbasis file
Petunjuk berikut menjelaskan proses cara melakukan pencadangan dan pemulihan data dengan image cadangan berbasis file:
Agen Pencadangan dan DR di-deploy di server database.
Pasang disk staging di server database.
Panggil pencadangan penuh menggunakan perintah pencadangan dump, yang menulis pencadangan
ke disk yang terpasang.
Backup and DR mengambil snapshot internal.
Pencadangan log dilakukan dengan cara yang serupa langsung dari sistem file pada
jadwal apa pun yang Anda konfigurasikan.
Untuk pemulihan data, Pencadangan dan DR langsung memasang disk staging ke
server database dan memulai operasi pemulihan database.
Log dapat diputar ke titik waktu mana pun setelah database dipulihkan.
Dokumentasi lainnya untuk Pencadangan dan DR untuk MySQL
Halaman ini adalah salah satu dari serangkaian halaman khusus untuk melindungi dan memulihkan database MySQL dengan Pencadangan dan DR. Anda dapat menemukan informasi tambahan di:
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-08-18 UTC."],[[["\u003cp\u003eBackup 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 \u003ccode\u003emysqldump\u003c/code\u003e API.\u003c/p\u003e\n"],["\u003cp\u003eVolume-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.\u003c/p\u003e\n"],["\u003cp\u003eFile-based backups use the \u003ccode\u003emysqldump\u003c/code\u003e API to write full backups to a mounted staging disk, and log backups are performed directly from the file-system.\u003c/p\u003e\n"],["\u003cp\u003eFor 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.\u003c/p\u003e\n"],["\u003cp\u003eMySQL binary logs can be purged via the \u003ccode\u003epurge binary logs before\u003c/code\u003e API during a log backup, which also copies all the binary logs.\u003c/p\u003e\n"]]],[],null,["# Backup and DR Service for MySQL\n\nMySQL is the world's most popular open source database, used by high profile web\nproperties.\nThis page explains how to protect MySQL application consistent database\ndata with Backup and DR in a Linux environment.\n\n**MySQL backup API used by Backup and DR**\n\n- **Volume level (Linux change block tracking and LVM snapshot) backups** :\n MySQL `Flush tables overwriting the data area. With read lock` and\n `Unlock tables` API.\n\n- **Full+Incremental (file-based traditional) backups** : MySQL `mysqldump`\n API. This provides the full backup of the database in backup\n format. On recovery, the restore db API recovers the database by physically\n overwriting the data area.\n\n- **MySQL log backup** : During a log backup, Backup and DR physically copies\n all the MySQL binary logs. The MySQL `purge binary logs before` API is used\n to purge the binary logs.\n\nHow it works: Backup and DR volume-based backup with Linux CBT\n--------------------------------------------------------------\n\nOnly changed blocks are tracked in the bitmap: no copy-on-writes, no I/O-intensive operations.\n\nData backup and recovery follows these steps:\n\n1. The Backup and DR agent has CBT to track changed blocks in the database data\n area.\n\n2. The agent calls the database API to freeze or pause database for data backup.\n\n3. Agent creates LVM snapshot of database data area and synthesizes a bitmap.\n\n4. Agent call to database API to unfreeze database.\n\n5. Agent copies changed blocks to backup/recovery appliance, which then deletes\n the snapshot and catalogs the backup.\n\n6. The appliance issues an internal snapshot and synthesizes a point-in-time\n virtual full backup.\n\n7. For data recovery, Backup and DR instantly mounts a rewritable staging disk\n and brings the database online.\n\nHow it works: file-based backup\n-------------------------------\n\nThe following instructions describe the process for how to perform data backup\nand recovery with file-based backup images:\n\n1. Backup and DR agent is deployed in the database server.\n\n2. Mount staging disk on the database server.\n\n3. Invoke full backup using the dump backup command, writing the backup\n to the mounted disk.\n\n4. Backup and DR takes an internal snapshot.\n Log backups are done in a similar fashion directly from the file-system at\n any schedule that you configure.\n\n5. For data recovery, Backup and DR instantly mounts the staging disk to the\n database server and initiates the database restore operation.\n Logs can be played to any point in time after the database is restored.\n\nWhat's next\n-----------\n\n[Prepare the database for Backup and DR](/backup-disaster-recovery/docs/configuration/otherdb-prep-database)\n\nOther documentation for Backup and DR for MySQL\n-----------------------------------------------\n\nThis page is one in a series of pages specific to protecting and recovering\nMySQL databases with Backup and DR.\nYou can find additional information at:\n\n- [Backup and DR for MySQL](/backup-disaster-recovery/docs/concepts/mysql-intro)\n- [Prepare the database for Backup and DR](/backup-disaster-recovery/docs/configuration/otherdb-prep-database)\n- [Add a MySQL database host and discover databases](/backup-disaster-recovery/docs/configuration/otherdb-add-host)\n- [Define policy templates and resource profiles](/backup-disaster-recovery/docs/create-plan/create-template)\n- [Set application details and settings](/backup-disaster-recovery/docs/backup/app-details-settings-otherdb)\n- [Check staging disk format and backup method](/backup-disaster-recovery/docs/backup/backup-method-staging-disk-otherdb)\n- [Protect the MySQL database and its logs](/backup-disaster-recovery/docs/backup/otherdb-protect)\n- [Mount a MySQL database](/backup-disaster-recovery/docs/access-data/otherdb-mounts)\n- [Recover MySQL Backups](/backup-disaster-recovery/docs/restore-data/otherdb-restore)\n- [Create a MySQL Backup and DR Workflow](/backup-disaster-recovery/docs/access-data/otherdb-workflow)"]]
