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.

Sign up for GitHub

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

Jump to bottom

log backup: reduce RPO to < 5m #11502

Merged
merged 4 commits into from
Dec 6, 2022
Merged

log backup: reduce RPO to < 5m #11502

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
c9bcac3
log backup: reduce RPO to < 5m
shichun-0415 Dec 1, 2022
2731df9
wording
shichun-0415 Dec 1, 2022
b45b14b
Merge remote-tracking branch 'upstream/master' into reduce-rpo
shichun-0415 Dec 2, 2022
cd169eb
update after refactor
shichun-0415 Dec 2, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
14 changes: 0 additions & 14 deletions br/pitr-known-issues.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,20 +7,6 @@ summary: Learn known issues in log backup.

This document lists the known issues and corresponding workarounds when you use the log backup feature.

## BR encounters the OOM problem after you run the `br log truncate` command

Issue: [#36648](https://github.com/pingcap/tidb/issues/36648)

Consider the following possible causes:

- The range of logs to be deleted is too large.

To resolve this issue, reduce the range of logs to be deleted first and delete the target logs in several batches instead of deleting them once.

- The memory allocation of the node where the BR process is located is too low.

It is recommended to scale up the node memory configuration to at least 16 GB to ensure that PITR has sufficient memory resources for recovery.

## The upstream database imports data using TiDB Lightning in the physical import mode, which makes it impossible to use the log backup feature

Currently, the log backup feature is not fully adapted to TiDB Lightning. Therefore, data imported in the physical mode of TiDB Lightning cannot be backed up to logs.
Expand Down
4 changes: 2 additions & 2 deletions br/point-in-time-recovery.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ Point-in-Time Recovery (PITR) allows you to restore a snapshot of a TiDB cluster

You can use PITR to meet the following business requirements:

- Reduce the Recovery Point Objective (RPO) of disaster recovery to less than 20 minutes.
- Reduce the Recovery Point Objective (RPO) of disaster recovery to less than 5 minutes.
- Handle the cases of incorrect writes from applications by rolling back data to a time point before the error event.
- Perform history data auditing to meet the requirements of laws and regulations.

Expand Down Expand Up @@ -56,7 +56,7 @@ To manage backup data for PITR, you need to design a backup directory structure
- PITR log backup has a 5% impact on the cluster.
- When you back up logs and snapshots at the same time, it has a less than 20% impact on the cluster.
- On each TiKV node, PITR can restore snapshot data at 280 GB/h and log data at 30 GB/h.
- With PITR, the RPO of disaster recovery is less than 20 minutes. Depending on the data size to be restored, the Recovery Time Objective (RTO) varies from several minutes to several hours.
- With PITR, the RPO of disaster recovery is less than 5 minutes. Depending on the data size to be restored, the Recovery Time Objective (RTO) varies from several minutes to several hours.
- BR deletes outdated log backup data at a speed of 600 GB/h.

> **Note:**
Expand Down