diff --git a/docs/user_docs/backup-and-restore/introduction.md b/docs/user_docs/backup-and-restore/introduction.md index 41c9c0a9d60..9bd01d55563 100644 --- a/docs/user_docs/backup-and-restore/introduction.md +++ b/docs/user_docs/backup-and-restore/introduction.md @@ -10,29 +10,22 @@ sidebar_label: Introduction KubeBlocks provides the backup and restore function to ensure the safety and reliability of your data. The backup and restore function of KubeBlocks relies on BackupRepo and before using the full backup and restore function, you need to [configure BackupRepo first](./backup/backup-repo.md). -KubeBlocks adopts physical backup which takes the physical files in a database as the backup object. +KubeBlocks adopts physical backup which takes the physical files in a database as the backup object. You can choose one backup option based on your demands to back up the cluster data on demand or by schedule. -* [On-demand backup](./backup/on-demand-backup.md): On-demand backup only contains full data, which can also be called full backup. Based on different backup options, on-demand backup can be further divided into backup tool and snapshot backup. +* [On-demand backup](./backup/on-demand-backup.md): Based on different backup options, on-demand backup can be further divided into backup tool and snapshot backup. * Backup tool: You can use the backup tool of the corresponding data product, such as MySQL XtraBackup and PostgreSQL pg_basebackup. KubeBlocks supports configuring backup tools for different data products. - * Snapshot backup: If your data is stored in a cloud disk that supports snapshots, you can create a data backup by snapshots. Snapshot backup is usually faster than backup tool, and thus is recommended. + * Snapshot backup: If your data is stored in a cloud disk that supports snapshots, you can create a data backup by snapshots. Snapshot backup is usually faster than a backup tool, and thus is recommended. -* [Scheduled backup](./backup/scheduled-backup.md): You can specify retention time, backup method, time, and other parameters to [customize your backup schedule](./backup/scheduled-backup.md#backup-by-schedule). Or you can backup your data automatically [by log](./backup/scheduled-backup.md#backup-automatically-by-log). Log backup uses the incremental log files generated by backing up the database, such as MySQL BinLog and PostgreSQL WAL, and it can also be called incremental backup. Point-in-time recovery (PITR) relies on log backup. +* [Scheduled backup](./backup/scheduled-backup.md): You can specify retention time, backup method, time, and other parameters to customize your backup schedule. As for the restore function, KubeBlocks supports restoring data from the backup set. * Restore * [Restore data from the backup set](./restore/restore-data-from-backup-set.md) -The backup and restore function for different database engines varies: - -| Engine | Scheduled Backup | Real-time Backup | Snapshot Backup | Datafile Backup | Log Backup | Full Backup | PITR | Data Compression | -| :----- | :--------------- | :--------------- | :-------------- | :---------- | :--------- | :---------- | :--- | :--------------- | -| PostgreSQL | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| ApeCloud MySQL | ✅ | ❌ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| MongoDB | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| Redis | ✅ | ❌ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ | -| Prometheus | ✅ | ❌ | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | -| Nebula | ✅ | ❌ | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | -| Milvus | ✅ | ❌ | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | -| Qdrant | ✅ | ❌ | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | -| Weaviate | ✅ | ❌ | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | +Follow the steps below to back up and restore your cluster. + +1. [Configure BackupRepo](./backup/backup-repo.md). +2. [Configure BackupPolicy](./backup/configure-backuppolicy.md). +3. Backup your cluster [on demand](./backup/on-demand-backup.md) or [by schedule](./backup/scheduled-backup.md). +4. [Restore your data](./restore/restore-data-from-backup-set.md) from the backup set. diff --git a/i18n/zh-cn/user-docs/backup-and-restore/overview.md b/i18n/zh-cn/user-docs/backup-and-restore/overview.md index 5599dd2c342..d84ad1c3272 100644 --- a/i18n/zh-cn/user-docs/backup-and-restore/overview.md +++ b/i18n/zh-cn/user-docs/backup-and-restore/overview.md @@ -7,30 +7,25 @@ sidebar_label: 简介 --- # 简介 + KubeBlocks 提供备份恢复功能，以确保数据的安全性和可靠性。KubeBlocks 的备份恢复功能依赖于 BackupRepo，在使用完整的备份恢复功能之前，首先需要配置 [BackupRepo](../backup-and-restore/backup/backup-repo.md)。 -KubeBlocks 采用物理备份的方式，将数据库中的物理文件作为备份对象。 +KubeBlocks 采用物理备份的方式，将数据库中的物理文件作为备份对象。你可以根据实际需求，选择对应的方式按需或定时备份集群数据。 -- [按需备份](../backup-and-restore/backup/on-demand-backup.md)：按需备份仅包含完整数据，也称为全量备份。根据不同的备份选项，按需备份可以进一步分为备份工具备份和快照备份两种。 +- [按需备份](../backup-and-restore/backup/on-demand-backup.md)：根据不同的备份选项，按需备份可以进一步分为备份工具备份和快照备份两种。 - 备份工具备份：可使用数据库产品的备份工具，如 MySQL XtraBackup 和 PostgreSQL pg_basebackup。KubeBlocks 支持为不同的数据产品配置备份工具。 - 快照备份：如果你的数据存储在支持快照的云盘中，你可以通过快照创建数据备份。快照备份通常比备份工具备份更快，因此推荐使用。 -- [定时备份](../backup-and-restore/backup/scheduled-backup.md)：可指定保留时间、备份方法、时间等参数来[自定义备份](../backup-and-restore/backup/scheduled-backup.md)。或者你可以通过[日志自动备份](../backup-and-restore/backup/scheduled-backup.md)。日志备份使用备份数据库生成的增量日志文件，如 MySQL BinLog 和 PostgreSQL WAL，因此也被称为增量备份。基于时间点的恢复（PITR）依赖于日志备份。 +- [定时备份](../backup-and-restore/backup/scheduled-backup.md)：可指定保留时间、备份方法、时间等参数来自定义备份设置。 + +KubeBlocks 支持从备份集中恢复数据。 -至于恢复功能，KubeBlocks 支持从备份集中恢复数据。 - 恢复 - - [从备份集中恢复数据](../backup-and-restore/restore/restore-data-from-backup-set.md) -不同数据库引擎的备份恢复功能有所不同： + - [从备份集中恢复数据](../backup-and-restore/restore/restore-data-from-backup-set.md) -引擎 | 定时备份 | 实时备份 | 快照备份 | 数据文件备份 | 日志备份 | 全量备份 | PITR | 数据压缩 | -:----- | :--------------- | :--------------- | :-------------- | :---------- | :--------- | :---------- | :--- | :--------------- | -PostgreSQL | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -ApeCloud MySQL | ✅ | ❌ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -MongoDB | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -Redis | ✅ | ❌ | ✅ | ✅ | ❌ | ✅ | ❌ | ✅ | -Prometheus | ✅ | ❌ | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | -Nebula | ✅ | ❌ | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | -Milvus | ✅ | ❌ | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | -Qdrant | ✅ | ❌ | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | -Weaviate | ✅ | ❌ | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | +可按照以下顺序对数据库集群进行备份和恢复操作。 +1. [配置 BackupRepo](./backup/backup-repo.md). +2. [配置 BackupPolicy](./backup/configure-backup-policy.md). +3. [定时备份](./backup/scheduled-backup.md)或者[按需备份](./backup/on-demand-backup.md)集群数据。 +4. 从备份集中[恢复集群数据](./restore/restore-data-from-backup-set.md)。