Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
MariaDB Backup API yang digunakan oleh Backup dan DR mencakup endpoint
berikut:
Snapshot LVM dan CBT Linux: MariaDB Flush tables with read lockUnlock tables API.
Pencadangan berbasis file: MariaDB mysqldump API. Tindakan ini akan menyediakan cadangan penuh database dalam format cadangan. Saat pemulihan, restore db API
memulihkan database dengan menimpa area data secara fisik.
Pencadangan log MariaDB: Selama pencadangan log, Backup and DR secara fisik menyalin
semua log biner MariaDB. API Purge binary logs before MariaDB
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 salin-saat-tulis atau
intensif I/O.
Langkah-langkah berikut menjelaskan proses cara melakukan pencadangan dan
pemulihan data dengan CBT dan image cadangan berbasis volume:
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
Langkah-langkah 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 Backup and DR untuk MariaDB
Halaman ini adalah salah satu dari serangkaian halaman khusus untuk melindungi dan memulihkan database MariaDB dengan Pencadangan dan DR. Anda dapat menemukan informasi tambahan di halaman berikut:
[[["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-09-03 UTC."],[[["\u003cp\u003eBackup and DR uses MariaDB APIs like \u003ccode\u003eFlush tables with read lock\u003c/code\u003e, \u003ccode\u003eUnlock tables\u003c/code\u003e, and \u003ccode\u003emysqldump\u003c/code\u003e for Linux CBT, LVM snapshot, and file-based backups.\u003c/p\u003e\n"],["\u003cp\u003eVolume-based backups with Linux CBT track changed blocks without copy-on-writes, utilizing LVM snapshots and database APIs to pause/unpause during the backup process.\u003c/p\u003e\n"],["\u003cp\u003eFile-based backups employ a staging disk mounted on the database server, where \u003ccode\u003emysqldump\u003c/code\u003e writes the full backup, and log backups are performed directly from the file system.\u003c/p\u003e\n"],["\u003cp\u003eRecovery for both volume-based and file-based methods involves instant mounting of a staging disk, with the option to play logs to any point in time after the file-based database is restored.\u003c/p\u003e\n"],["\u003cp\u003eBackup and DR provides comprehensive documentation on protecting and recovering MariaDB databases, including preparation, policy creation, application settings, and workflow creation.\u003c/p\u003e\n"]]],[],null,["# Backup and DR Service for MariaDB\n\nThe MariaDB Backup API used by Backup and DR includes the following\nendpoints:\n\n- **Linux CBT and LVM snapshot** : MariaDB `Flush tables with read lock`\n `Unlock tables` API.\n\n- **File-based backups** : MariaDB `mysqldump` API. This provides the full\n backup of the database in backup format. On recovery, the `restore db` API\n recovers the database by physically overwriting the data area.\n\n- **MariaDB log backup** : During a log backup, Backup and DR physically copies\n all the MariaDB binary logs. The MariaDB `Purge binary logs before`\n API is used 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, there are no copy-on-writes or\nI/O-intensive operations.\n\nThe following steps describe the process for how to perform data backup and\nrecovery with volume-based backup images and CBT:\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 steps describe the process for how to perform data backup and\nrecovery 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 MariaDB\n-------------------------------------------------\n\nThis page is one in a series of pages specific to protecting and recovering\nMariaDB databases with Backup and DR.\nYou can find additional information in the following pages:\n\n- [Backup and DR for MariaDB](/backup-disaster-recovery/docs/concepts/mariadb-intro)\n- [Prepare the database for Backup and DR](/backup-disaster-recovery/docs/configuration/otherdb-prep-database)\n- [Add a MariaDB 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 MariaDB database and its logs](/backup-disaster-recovery/docs/backup/otherdb-protect)\n- [Mount a MariaDB database](/backup-disaster-recovery/docs/access-data/otherdb-mounts)\n- [Recover MariaDB Backups](/backup-disaster-recovery/docs/restore-data/otherdb-restore)\n- [Create a MariaDB Backup and DR Workflow](/backup-disaster-recovery/docs/access-data/otherdb-workflow)"]]
