Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update 3.backup-data.md #1898

Merged
merged 1 commit into from
Feb 2, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs-2.0/backup-and-restore/nebula-br-ent/3.backup-data.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ You can use BR (Enterprise Edition) to back up NebulaGraph data. You can perform
- During the process of a full backup, it may take a long time if the amount of the data to be backed up is large.
- During the process of data backup, DDL and DML statements in the specified graph space are blocked. We recommend that you perform the backup operation during the low business peak period.
- The cluster performing an incremental backup needs to be the same as the cluster specified for the previous backup. The storage path of the incremental backup should also be the same as the path of the previous backup.
- Make sure that the time between each incremental backup and the first backup is less than one [`wal_ttl`](../../5.configurations-and-logs/1.configurations/4.storage-config.md).
- Make sure that the time between each incremental backup and the last backup is less than a [`wal_ttl`](../../5.configurations-and-logs/1.configurations/4.storage-config.md) time.
- Make sure that Agent has read and write permissions for the corresponding NebulaGraph cluster installation directory and backup directory.

## Prerequisites
Expand Down