diff --git a/br/.dockerignore b/br/.dockerignore
deleted file mode 120000
index 3e4e48b0b5fe6..0000000000000
--- a/br/.dockerignore
+++ /dev/null
@@ -1 +0,0 @@
-.gitignore
\ No newline at end of file
diff --git a/br/.editorconfig b/br/.editorconfig
deleted file mode 100644
index 43c6a002cce45..0000000000000
--- a/br/.editorconfig
+++ /dev/null
@@ -1,10 +0,0 @@
-[*]
-end_of_line = lf
-insert_final_newline = true
-charset = utf-8
-
-# tab_size = 4 spaces
-[*.go]
-indent_style = tab
-indent_size = 4
-trim_trailing_whitespace = true
diff --git a/br/.gitattributes b/br/.gitattributes
deleted file mode 100644
index ba35fa1000ef6..0000000000000
--- a/br/.gitattributes
+++ /dev/null
@@ -1 +0,0 @@
-*_generated.go linguist-generated=true
diff --git a/br/.gitignore b/br/.gitignore
deleted file mode 100644
index c29d04732ce40..0000000000000
--- a/br/.gitignore
+++ /dev/null
@@ -1,14 +0,0 @@
-/br
-/bin
-/.idea
-/docker/data/
-/docker/logs/
-*.swp
-.DS_Store
-/go.mod
-/go.sum
-
-# for the web interface
-web/node_modules/
-web/dist/
-.vscode/
diff --git a/br/.golangci.yml b/br/.golangci.yml
deleted file mode 100644
index 0cb2a9b651251..0000000000000
--- a/br/.golangci.yml
+++ /dev/null
@@ -1,12 +0,0 @@
-linters-settings:
-  gocyclo:
-    min-complexity: 40
-
-issues:
-  # Excluding configuration per-path, per-linter, per-text and per-source
-  exclude-rules:
-    # TODO Remove it.
-    - path: split_client.go
-      text: "SA1019:"
-      linters:
-        - staticcheck
diff --git a/br/COMPATIBILITY_TEST.md b/br/COMPATIBILITY_TEST.md
deleted file mode 100644
index 44984ebcd2bfa..0000000000000
--- a/br/COMPATIBILITY_TEST.md
+++ /dev/null
@@ -1,42 +0,0 @@
-# Compatibility test
-
-## Background
-
-We had some incompatibility issues in the past, which made BR cannot restore backed up data in some situations.
-So we need a test workflow to check the compatibility.
-
-## Goal
-
-- Ensure backward compatibility for restoring data from the previous 3 minor versions
-
-## Workflow
-
-### Data Preparation
-
-This workflow needs previous backup data. To get this data. we perform the following steps
-
-- Run a TiDB cluster with previous version.
-- Run backup jobs with corresponding BR version, with different storages (s3, gcs).
-
-Given we test for the previous 3 versions, and there are 2 different storage systems, we will produce 6 backup archives for 6 separate compatibility tests.
-
-### Test Content
-
-- Start TiDB cluster with nightly version.
-- Build BR binary with current directory.
-- Use BR to restore different version backup data one by one.
-- Make sure restore data is expected.
-
-### Running tests
-
-Start a cluster with docker-compose and Build br with latest version.
-
-```sh
-docker-compose -f docker-compose.yaml rm -s -v && \
-docker-compose -f docker-compose.yaml build && \
-docker-compose -f docker-compose.yaml up --remove-orphans
-```
-
-```sh
-docker-compose -f docker-compose.yaml control make compatibility_test
-```
diff --git a/br/CONTRIBUTING.md b/br/CONTRIBUTING.md
deleted file mode 100644
index 1f2846471a7a1..0000000000000
--- a/br/CONTRIBUTING.md
+++ /dev/null
@@ -1,90 +0,0 @@
-# How to contribute
-
-This document outlines some of the conventions on development workflow, commit
-message formatting, contact points and other resources to make it easier to get
-your contribution accepted.
-
-## Getting started
-
-- Fork the repository on GitHub.
-- Read the README.md for build instructions.
-- Play with the project, submit bugs, submit patches!
-
-## Building BR
-
-Developing BR requires:
-
-* [Go 1.16+](http://golang.org/doc/code.html)
-* An internet connection to download the dependencies
-
-Simply run `make` to build the program.
-
-```sh
-make
-```
-
-### Running tests
-
-This project contains unit tests and integration tests with coverage collection.
-See [tests/README.md](./tests/README.md) for how to execute and add tests.
-
-### Updating dependencies
-
-BR uses [Go 1.11 module](https://github.com/golang/go/wiki/Modules) to manage dependencies.
-To add or update a dependency: use the `go mod edit` command to change the dependency.
-
-## Contribution flow
-
-This is a rough outline of what a contributor's workflow looks like:
-
-- Create a topic branch from where you want to base your work. This is usually `master`.
-- Make commits of logical units and add test case if the change fixes a bug or adds new functionality.
-- Run tests and make sure all the tests are passed.
-- Make sure your commit messages are in the proper format (see below).
-- Push your changes to a topic branch in your fork of the repository.
-- Submit a pull request.
-- Your PR must receive LGTMs from two maintainers.
-
-Thanks for your contributions!
-
-### Code style
-
-The coding style suggested by the Golang community is used in BR.
-See the [style doc](https://github.com/golang/go/wiki/CodeReviewComments) for details.
-
-Please follow this style to make BR easy to review, maintain and develop.
-
-### Format of the Commit Message
-
-We follow a rough convention for commit messages that is designed to answer two
-questions: what changed and why. The subject line should feature the what and
-the body of the commit should describe the why.
-
-```
-restore: add comment for variable declaration
-
-Improve documentation.
-```
-
-The format can be described more formally as follows:
-
-```
-<subsystem>: <what changed>
-<BLANK LINE>
-<why this change was made>
-<BLANK LINE>
-<footer>(optional)
-```
-
-The first line is the subject and should be no longer than 70 characters, the
-second line is always blank, and other lines should be wrapped at 80 characters.
-This allows the message to be easier to read on GitHub as well as in various
-git tools.
-
-If the change affects more than one subsystem, you can use comma to separate them like `backup,restore:`.
-
-If the change affects many subsystems, you can use ```*``` instead, like ```*:```.
-
-For the why part, if no specific reason for the change,
-you can use one of some generic reasons like "Improve documentation.",
-"Improve performance.", "Improve robustness.", "Improve test coverage."
\ No newline at end of file
diff --git a/br/LICENSE.md b/br/LICENSE.md
deleted file mode 100644
index 4eedc0116add7..0000000000000
--- a/br/LICENSE.md
+++ /dev/null
@@ -1,201 +0,0 @@
-Apache License
-                           Version 2.0, January 2004
-                        http://www.apache.org/licenses/
-
-   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
-   1. Definitions.
-
-      "License" shall mean the terms and conditions for use, reproduction,
-      and distribution as defined by Sections 1 through 9 of this document.
-
-      "Licensor" shall mean the copyright owner or entity authorized by
-      the copyright owner that is granting the License.
-
-      "Legal Entity" shall mean the union of the acting entity and all
-      other entities that control, are controlled by, or are under common
-      control with that entity. For the purposes of this definition,
-      "control" means (i) the power, direct or indirect, to cause the
-      direction or management of such entity, whether by contract or
-      otherwise, or (ii) ownership of fifty percent (50%) or more of the
-      outstanding shares, or (iii) beneficial ownership of such entity.
-
-      "You" (or "Your") shall mean an individual or Legal Entity
-      exercising permissions granted by this License.
-
-      "Source" form shall mean the preferred form for making modifications,
-      including but not limited to software source code, documentation
-      source, and configuration files.
-
-      "Object" form shall mean any form resulting from mechanical
-      transformation or translation of a Source form, including but
-      not limited to compiled object code, generated documentation,
-      and conversions to other media types.
-
-      "Work" shall mean the work of authorship, whether in Source or
-      Object form, made available under the License, as indicated by a
-      copyright notice that is included in or attached to the work
-      (an example is provided in the Appendix below).
-
-      "Derivative Works" shall mean any work, whether in Source or Object
-      form, that is based on (or derived from) the Work and for which the
-      editorial revisions, annotations, elaborations, or other modifications
-      represent, as a whole, an original work of authorship. For the purposes
-      of this License, Derivative Works shall not include works that remain
-      separable from, or merely link (or bind by name) to the interfaces of,
-      the Work and Derivative Works thereof.
-
-      "Contribution" shall mean any work of authorship, including
-      the original version of the Work and any modifications or additions
-      to that Work or Derivative Works thereof, that is intentionally
-      submitted to Licensor for inclusion in the Work by the copyright owner
-      or by an individual or Legal Entity authorized to submit on behalf of
-      the copyright owner. For the purposes of this definition, "submitted"
-      means any form of electronic, verbal, or written communication sent
-      to the Licensor or its representatives, including but not limited to
-      communication on electronic mailing lists, source code control systems,
-      and issue tracking systems that are managed by, or on behalf of, the
-      Licensor for the purpose of discussing and improving the Work, but
-      excluding communication that is conspicuously marked or otherwise
-      designated in writing by the copyright owner as "Not a Contribution."
-
-      "Contributor" shall mean Licensor and any individual or Legal Entity
-      on behalf of whom a Contribution has been received by Licensor and
-      subsequently incorporated within the Work.
-
-   2. Grant of Copyright License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      copyright license to reproduce, prepare Derivative Works of,
-      publicly display, publicly perform, sublicense, and distribute the
-      Work and such Derivative Works in Source or Object form.
-
-   3. Grant of Patent License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      (except as stated in this section) patent license to make, have made,
-      use, offer to sell, sell, import, and otherwise transfer the Work,
-      where such license applies only to those patent claims licensable
-      by such Contributor that are necessarily infringed by their
-      Contribution(s) alone or by combination of their Contribution(s)
-      with the Work to which such Contribution(s) was submitted. If You
-      institute patent litigation against any entity (including a
-      cross-claim or counterclaim in a lawsuit) alleging that the Work
-      or a Contribution incorporated within the Work constitutes direct
-      or contributory patent infringement, then any patent licenses
-      granted to You under this License for that Work shall terminate
-      as of the date such litigation is filed.
-
-   4. Redistribution. You may reproduce and distribute copies of the
-      Work or Derivative Works thereof in any medium, with or without
-      modifications, and in Source or Object form, provided that You
-      meet the following conditions:
-
-      (a) You must give any other recipients of the Work or
-          Derivative Works a copy of this License; and
-
-      (b) You must cause any modified files to carry prominent notices
-          stating that You changed the files; and
-
-      (c) You must retain, in the Source form of any Derivative Works
-          that You distribute, all copyright, patent, trademark, and
-          attribution notices from the Source form of the Work,
-          excluding those notices that do not pertain to any part of
-          the Derivative Works; and
-
-      (d) If the Work includes a "NOTICE" text file as part of its
-          distribution, then any Derivative Works that You distribute must
-          include a readable copy of the attribution notices contained
-          within such NOTICE file, excluding those notices that do not
-          pertain to any part of the Derivative Works, in at least one
-          of the following places: within a NOTICE text file distributed
-          as part of the Derivative Works; within the Source form or
-          documentation, if provided along with the Derivative Works; or,
-          within a display generated by the Derivative Works, if and
-          wherever such third-party notices normally appear. The contents
-          of the NOTICE file are for informational purposes only and
-          do not modify the License. You may add Your own attribution
-          notices within Derivative Works that You distribute, alongside
-          or as an addendum to the NOTICE text from the Work, provided
-          that such additional attribution notices cannot be construed
-          as modifying the License.
-
-      You may add Your own copyright statement to Your modifications and
-      may provide additional or different license terms and conditions
-      for use, reproduction, or distribution of Your modifications, or
-      for any such Derivative Works as a whole, provided Your use,
-      reproduction, and distribution of the Work otherwise complies with
-      the conditions stated in this License.
-
-   5. Submission of Contributions. Unless You explicitly state otherwise,
-      any Contribution intentionally submitted for inclusion in the Work
-      by You to the Licensor shall be under the terms and conditions of
-      this License, without any additional terms or conditions.
-      Notwithstanding the above, nothing herein shall supersede or modify
-      the terms of any separate license agreement you may have executed
-      with Licensor regarding such Contributions.
-
-   6. Trademarks. This License does not grant permission to use the trade
-      names, trademarks, service marks, or product names of the Licensor,
-      except as required for reasonable and customary use in describing the
-      origin of the Work and reproducing the content of the NOTICE file.
-
-   7. Disclaimer of Warranty. Unless required by applicable law or
-      agreed to in writing, Licensor provides the Work (and each
-      Contributor provides its Contributions) on an "AS IS" BASIS,
-      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-      implied, including, without limitation, any warranties or conditions
-      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
-      PARTICULAR PURPOSE. You are solely responsible for determining the
-      appropriateness of using or redistributing the Work and assume any
-      risks associated with Your exercise of permissions under this License.
-
-   8. Limitation of Liability. In no event and under no legal theory,
-      whether in tort (including negligence), contract, or otherwise,
-      unless required by applicable law (such as deliberate and grossly
-      negligent acts) or agreed to in writing, shall any Contributor be
-      liable to You for damages, including any direct, indirect, special,
-      incidental, or consequential damages of any character arising as a
-      result of this License or out of the use or inability to use the
-      Work (including but not limited to damages for loss of goodwill,
-      work stoppage, computer failure or malfunction, or any and all
-      other commercial damages or losses), even if such Contributor
-      has been advised of the possibility of such damages.
-
-   9. Accepting Warranty or Additional Liability. While redistributing
-      the Work or Derivative Works thereof, You may choose to offer,
-      and charge a fee for, acceptance of support, warranty, indemnity,
-      or other liability obligations and/or rights consistent with this
-      License. However, in accepting such obligations, You may act only
-      on Your own behalf and on Your sole responsibility, not on behalf
-      of any other Contributor, and only if You agree to indemnify,
-      defend, and hold each Contributor harmless for any liability
-      incurred by, or claims asserted against, such Contributor by reason
-      of your accepting any such warranty or additional liability.
-
-   END OF TERMS AND CONDITIONS
-
-   APPENDIX: How to apply the Apache License to your work.
-
-      To apply the Apache License to your work, attach the following
-      boilerplate notice, with the fields enclosed by brackets "{}"
-      replaced with your own identifying information. (Don't include
-      the brackets!)  The text should be enclosed in the appropriate
-      comment syntax for the file format. We also recommend that a
-      file or class name and description of purpose be included on the
-      same "printed page" as the copyright notice for easier
-      identification within third-party archives.
-
-   Copyright [yyyy] [name of copyright owner]
-
-   Licensed under the Apache License, Version 2.0 (the "License");
-   you may not use this file except in compliance with the License.
-   You may obtain a copy of the License at
-
-       http://www.apache.org/licenses/LICENSE-2.0
-
-   Unless required by applicable law or agreed to in writing, software
-   distributed under the License is distributed on an "AS IS" BASIS,
-   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-   See the License for the specific language governing permissions and
-   limitations under the License.
diff --git a/br/README.md b/br/README.md
deleted file mode 100644
index 8e8aaf40f45f6..0000000000000
--- a/br/README.md
+++ /dev/null
@@ -1,137 +0,0 @@
-# BR
-
-[![Build Status](https://internal.pingcap.net/idc-jenkins/job/build_br_multi_branch/job/master/badge/icon)](https://internal.pingcap.net/idc-jenkins/job/build_br_multi_branch/job/master/)
-[![codecov](https://codecov.io/gh/pingcap/br/branch/master/graph/badge.svg)](https://codecov.io/gh/pingcap/br)
-[![LICENSE](https://img.shields.io/github/license/pingcap/br.svg)](https://github.com/pingcap/br/blob/master/LICENSE)
-[![Language](https://img.shields.io/badge/Language-Go-blue.svg)](https://golang.org/)
-[![GoDoc](https://img.shields.io/badge/Godoc-reference-blue.svg)](https://godoc.org/github.com/pingcap/br)
-[![Go Report Card](https://goreportcard.com/badge/github.com/pingcap/br)](https://goreportcard.com/report/github.com/pingcap/br)
-[![GitHub release](https://img.shields.io/github/tag/pingcap/br.svg?label=release)](https://github.com/pingcap/br/releases)
-[![GitHub release date](https://img.shields.io/github/release-date/pingcap/br.svg)](https://github.com/pingcap/br/releases)
-
-**Backup & Restore (BR)** is a command-line tool for distributed backup and restoration of the TiDB cluster data.
-
-## Architecture
-
-<img src="images/arch.svg?sanitize=true" alt="architecture" width="600"/>
-
-## Documentation
-
-[Chinese Document](https://docs.pingcap.com/zh/tidb/stable/backup-and-restore-overview)
-
-[English Document](https://docs.pingcap.com/tidb/stable/backup-and-restore-overview)
-
-[Backup SQL Statement](https://docs.pingcap.com/tidb/stable/sql-statement-backup)
-
-[Restore SQL Statement](https://docs.pingcap.com/tidb/stable/sql-statement-restore)
-
-## Building
-
-To build binary and run test:
-
-```bash
-$ make
-$ make test
-```
-
-Notice BR supports building with Go version `Go >= 1.16`
-
-When BR is built successfully, you can find binary in the `bin` directory.
-
-## Quick start(docker-compose)
-
-```sh
-# Start TiDB cluster
-docker-compose -f docker-compose.yaml rm -s -v && \
-docker-compose -f docker-compose.yaml build && \
-docker-compose -f docker-compose.yaml up --remove-orphans
-
-# Attach to control container to run BR
-docker exec -it br_control_1 bash
-
-# Load testing data to TiDB
-go-ycsb load mysql -p workload=core \
-    -p mysql.host=tidb -p mysql.port=4000 -p mysql.user=root \
-    -p recordcount=100000 -p threadcount=100
-
-# How many rows do we get? 100000 rows.
-mysql -uroot -htidb -P4000 -E -e "SELECT COUNT(*) FROM test.usertable"
-
-# Build BR and backup!
-make build && \
-bin/br backup full --pd pd0:2379 --storage "local:///data/backup/full" \
-    --log-file "/logs/br_backup.log"
-
-# Let's drop database.
-mysql -uroot -htidb -P4000 -E -e "DROP DATABASE test; SHOW DATABASES;"
-
-# Restore!
-bin/br restore full --pd pd0:2379 --storage "local:///data/backup/full" \
-    --log-file "/logs/br_restore.log"
-
-# How many rows do we get again? Expected to be 100000 rows.
-mysql -uroot -htidb -P4000 -E -e "SELECT COUNT(*) FROM test.usertable"
-
-# Test S3 compatible storage (MinIO).
-# Create a bucket to save backup by mc (a MinIO Client).
-mc config host add minio $S3_ENDPOINT $MINIO_ACCESS_KEY $MINIO_SECRET_KEY && \
-mc mb minio/mybucket
-
-# Backup to S3 compatible storage.
-bin/br backup full --pd pd0:2379 --storage "s3://mybucket/full" \
-    --s3.endpoint="$S3_ENDPOINT"
-
-# Drop database and restore!
-mysql -uroot -htidb -P4000 -E -e "DROP DATABASE test; SHOW DATABASES;" && \
-bin/br restore full --pd pd0:2379 --storage "s3://mybucket/full" \
-    --s3.endpoint="$S3_ENDPOINT"
-```
-
-## Quick Start(tiup)
-
-```sh
-# Using tiup to start a TiDB cluster
-tiup playground --db 2 --pd 3 --kv 3 --monitor
-
-# Using tiup bench to generater test data.
-tiup bench tpcc --warehouses 1 prepare
-
-# How many row do we get? 300242 rows.
-mysql --host 127.0.0.1 --port 4000 -E -e "SELECT COUNT(*) FROM test.order_line" -u root -p
-
-# Build br.
-make build
-
-# Backup TPC-C test data.
-bin/br backup table --db test \
-	--table order_line \
-	-s local:///tmp/backup_test/ \
-	--pd ${PD_ADDR}:2379 \
-	--log-file backup_test.log \
-
-# Let's drop the table.
-mysql -uroot --host 127.0.0.1 -P4000 -E -e "USE test; DROP TABLE order_line; show tables" -u root -p
-
-# Restore from the backup.
-bin/br restore table --db test \
-	--table order_line \
-	-s local:///tmp/backup_test/ \
-	--pd ${PD_ADDR}:2379 \
-	--log-file restore_test.log
-
-# How many rows do we get after restore? Expected to be 300242 rows.
-mysql --host 127.0.0.1 -P4000 -E -e "SELECT COUNT(*) FROM test.order_line" -uroot -p
-```
-
-## Compatibility test
-
-See [COMPATBILE_TEST](./COMPATIBILITY_TEST.md)
-
-## Contributing
-
-Contributions are welcomed and greatly appreciated. See [CONTRIBUTING](./CONTRIBUTING.md)
-for details on submitting patches and the contribution workflow.
-
-## License
-
-BR is under the Apache 2.0 license. See the [LICENSE](./LICENSE.md) file for details.
diff --git a/br/SECURITY.md b/br/SECURITY.md
deleted file mode 100644
index 5d255ecc936bb..0000000000000
--- a/br/SECURITY.md
+++ /dev/null
@@ -1,33 +0,0 @@
-# Security Vulnerability Disclosure and Response Process
-
-TiDB is a fast-growing open source database. To ensure its security, a security vulnerability disclosure and response process is adopted.
-
-The primary goal of this process is to reduce the total exposure time of users to publicly known vulnerabilities. To quickly fix vulnerabilities of TiDB products, the security team is responsible for the entire vulnerability management process, including internal communication and external disclosure.
-
-If you find a vulnerability or encounter a security incident involving vulnerabilities of TiDB products, please report it as soon as possible to the TiDB security team (security@tidb.io).
-
-Please kindly help provide as much vulnerability information as possible in the following format:
-
-- Issue title*:
-
-- Overview*:
-
-- Affected components and version number*:
-
-- CVE number (if any):
-
-- Vulnerability verification process*:
-
-- Contact information*:
-
-The asterisk (*) indicates the required field.
-
-# Response Time
-
-The TiDB security team will confirm the vulnerabilities and contact you within 2 working days after your submission.
-
-We will publicly thank you after fixing the security vulnerability. To avoid negative impact, please keep the vulnerability confidential until we fix it. We would appreciate it if you could obey the following code of conduct:
-
-The vulnerability will not be disclosed until TiDB releases a patch for it.
-
-The details of the vulnerability, for example, exploits code, will not be disclosed.
diff --git a/br/docker-compose.yaml b/br/docker-compose.yaml
deleted file mode 100644
index ccf2a734ee5e5..0000000000000
--- a/br/docker-compose.yaml
+++ /dev/null
@@ -1,224 +0,0 @@
----
-# Source: tidb-docker-compose/templates/docker-compose.yml
-version: '3.2'
-
-services:
-  control:
-    image: control:nightly
-    build:
-      context: .
-      dockerfile: ./docker/Dockerfile
-    volumes:
-      - /tmp/br/docker/data:/data
-      - /tmp/br/docker/logs:/tmp
-      - /tmp/br/docker/logs:/logs
-      - ./bin:/go/src/github.com/pingcap/br/bin
-    command: -c "/usr/bin/tail -f /dev/null"
-    depends_on:
-      - "tidb"
-    restart: on-failure
-    env_file:
-      - ./docker/minio.env
-
-  pd0:
-    image: pingcap/pd:nightly
-    ports:
-      - "2379"
-    volumes:
-      - ./docker/config/pd.toml:/pd.toml:ro
-      - /tmp/br/docker/data:/data
-      - /tmp/br/docker/logs:/logs
-    command:
-      - --name=pd0
-      - --client-urls=http://0.0.0.0:2379
-      - --peer-urls=http://0.0.0.0:2380
-      - --advertise-client-urls=http://pd0:2379
-      - --advertise-peer-urls=http://pd0:2380
-      - --initial-cluster=pd0=http://pd0:2380
-      - --data-dir=/data/pd0
-      - --config=/pd.toml
-      - --log-file=/logs/pd0.log
-    # sysctls:
-    #   net.core.somaxconn: 32768
-    # ulimits:
-    #   nofile:
-    #     soft: 1000000
-    #     hard: 1000000
-    restart: on-failure
-
-  tikv0:
-    image: pingcap/tikv:nightly
-    volumes:
-      - ./docker/config/tikv.toml:/tikv.toml:ro
-      - /tmp/br/docker/data:/data
-      - /tmp/br/docker/logs:/logs
-    command:
-      - --addr=0.0.0.0:20160
-      - --advertise-addr=tikv0:20160
-      - --data-dir=/data/tikv0
-      - --pd=pd0:2379
-      - --config=/tikv.toml
-      - --log-file=/logs/tikv0.log
-    depends_on:
-      - "pd0"
-    # sysctls:
-    #   net.core.somaxconn: 32768
-    # ulimits:
-    #   nofile:
-    #     soft: 1000000
-    #     hard: 1000000
-    restart: on-failure
-    env_file:
-      - ./docker/minio.env
-
-  tikv1:
-    image: pingcap/tikv:nightly
-    volumes:
-      - ./docker/config/tikv.toml:/tikv.toml:ro
-      - /tmp/br/docker/data:/data
-      - /tmp/br/docker/logs:/logs
-    command:
-      - --addr=0.0.0.0:20160
-      - --advertise-addr=tikv1:20160
-      - --data-dir=/data/tikv1
-      - --pd=pd0:2379
-      - --config=/tikv.toml
-      - --log-file=/logs/tikv1.log
-    depends_on:
-      - "pd0"
-    # sysctls:
-    #   net.core.somaxconn: 32768
-    # ulimits:
-    #   nofile:
-    #     soft: 1000000
-    #     hard: 1000000
-    restart: on-failure
-    env_file:
-      - ./docker/minio.env
-
-  tikv2:
-    image: pingcap/tikv:nightly
-    volumes:
-      - ./docker/config/tikv.toml:/tikv.toml:ro
-      - /tmp/br/docker/data:/data
-      - /tmp/br/docker/logs:/logs
-    command:
-      - --addr=0.0.0.0:20160
-      - --advertise-addr=tikv2:20160
-      - --data-dir=/data/tikv2
-      - --pd=pd0:2379
-      - --config=/tikv.toml
-      - --log-file=/logs/tikv2.log
-    depends_on:
-      - "pd0"
-    # sysctls:
-    #   net.core.somaxconn: 32768
-    # ulimits:
-    #   nofile:
-    #     soft: 1000000
-    #     hard: 1000000
-    restart: on-failure
-    env_file:
-      - ./docker/minio.env
-
-  tikv3:
-    image: pingcap/tikv:nightly
-    volumes:
-      - ./docker/config/tikv.toml:/tikv.toml:ro
-      - /tmp/br/docker/data:/data
-      - /tmp/br/docker/logs:/logs
-    command:
-      - --addr=0.0.0.0:20160
-      - --advertise-addr=tikv3:20160
-      - --data-dir=/data/tikv3
-      - --pd=pd0:2379
-      - --config=/tikv.toml
-      - --log-file=/logs/tikv3.log
-    depends_on:
-      - "pd0"
-    # sysctls:
-    #   net.core.somaxconn: 32768
-    # ulimits:
-    #   nofile:
-    #     soft: 1000000
-    #     hard: 1000000
-    restart: on-failure
-    env_file:
-      - ./docker/minio.env
-
-  tikv4:
-    image: pingcap/tikv:nightly
-    volumes:
-      - ./docker/config/tikv.toml:/tikv.toml:ro
-      - /tmp/br/docker/data:/data
-      - /tmp/br/docker/logs:/logs
-    command:
-      - --addr=0.0.0.0:20160
-      - --advertise-addr=tikv4:20160
-      - --data-dir=/data/tikv4
-      - --pd=pd0:2379
-      - --config=/tikv.toml
-      - --log-file=/logs/tikv4.log
-    depends_on:
-      - "pd0"
-    # sysctls:
-    #   net.core.somaxconn: 32768
-    # ulimits:
-    #   nofile:
-    #     soft: 1000000
-    #     hard: 1000000
-    restart: on-failure
-    env_file:
-      - ./docker/minio.env
-
-  tidb:
-    image: pingcap/tidb:nightly
-    ports:
-      - "4000"
-      - "10080"
-    volumes:
-      - ./docker/config/tidb.toml:/tidb.toml:ro
-      - /tmp/br/docker/logs:/logs
-    command:
-      - --store=tikv
-      - --path=pd0:2379
-      - --config=/tidb.toml
-      - --log-file=/logs/tidb.log
-      - --advertise-address=tidb
-    depends_on:
-      - "tikv0"
-      - "tikv1"
-      - "tikv2"
-      - "tikv3"
-      - "tikv4"
-    # sysctls:
-    #   net.core.somaxconn: 32768
-    # ulimits:
-    #   nofile:
-    #     soft: 1000000
-    #     hard: 1000000
-    restart: on-failure
-
-  minio:
-    image: minio/minio
-    ports:
-      - 24927:24927
-    volumes:
-      - /tmp/br/docker/data/s3:/data/s3
-    command: server --address=:24927 /data/s3
-    env_file:
-      - ./docker/minio.env
-
-  gcs:
-    image: fsouza/fake-gcs-server
-    ports:
-      - 20818:20818
-    volumes:
-      - /tmp/br/docker/data/gcs:/data/gcs
-    command: -scheme http -host gcs -port 20818 -filesystem-root /data/gcs -public-host gcs:20818
-
-  # we need a oauth server for gcs test
-  oauth:
-    image: 3pointer/fake-gcs-oauth
-    ports:
-      - 5000:5000
diff --git a/br/errors.toml b/br/errors.toml
deleted file mode 100644
index 7bdba0aeb0fcc..0000000000000
--- a/br/errors.toml
+++ /dev/null
@@ -1,213 +0,0 @@
-# AUTOGENERATED BY github.com/pingcap/errors/errdoc-gen
-# YOU CAN CHANGE THE 'description'/'workaround' FIELDS IF THEM ARE IMPROPER.
-
-["BR:Backup:ErrBackupChecksumMismatch"]
-error = '''
-backup checksum mismatch
-'''
-
-["BR:Backup:ErrBackupGCSafepointExceeded"]
-error = '''
-backup GC safepoint exceeded
-'''
-
-["BR:Backup:ErrBackupInvalidRange"]
-error = '''
-backup range invalid
-'''
-
-["BR:Backup:ErrBackupNoLeader"]
-error = '''
-backup no leader
-'''
-
-["BR:Common:ErrFailedToConnect"]
-error = '''
-failed to make gRPC channels
-'''
-
-["BR:Common:ErrInvalidArgument"]
-error = '''
-invalid argument
-'''
-
-["BR:Common:ErrInvalidMetaFile"]
-error = '''
-invalid metafile
-'''
-
-["BR:Common:ErrUndefinedDbOrTable"]
-error = '''
-undefined restore databases or tables
-'''
-
-["BR:Common:ErrUnknown"]
-error = '''
-internal error
-'''
-
-["BR:Common:ErrVersionMismatch"]
-error = '''
-version mismatch
-'''
-
-["BR:ExternalStorage:ErrStorageInvalidConfig"]
-error = '''
-invalid external storage config
-'''
-
-["BR:ExternalStorage:ErrStorageInvalidPermission"]
-error = '''
-external storage permission
-'''
-
-["BR:ExternalStorage:ErrStorageUnknown"]
-error = '''
-unknown external storage error
-'''
-
-["BR:KV:ErrKVClusterIDMismatch"]
-error = '''
-tikv cluster ID mismatch
-'''
-
-["BR:KV:ErrKVDownloadFailed"]
-error = '''
-download sst failed
-'''
-
-["BR:KV:ErrKVEpochNotMatch"]
-error = '''
-epoch not match
-'''
-
-["BR:KV:ErrKVIngestFailed"]
-error = '''
-ingest sst failed
-'''
-
-["BR:KV:ErrKVKeyNotInRegion"]
-error = '''
-key not in region
-'''
-
-["BR:KV:ErrKVNotLeader"]
-error = '''
-not leader
-'''
-
-["BR:KV:ErrKVRangeIsEmpty"]
-error = '''
-range is empty
-'''
-
-["BR:KV:ErrKVRewriteRuleNotFound"]
-error = '''
-rewrite rule not found
-'''
-
-["BR:KV:ErrKVStorage"]
-error = '''
-tikv storage occur I/O error
-'''
-
-["BR:KV:ErrKVUnknown"]
-error = '''
-unknown error occur on tikv
-'''
-
-["BR:KV:ErrNotTiKVStorage"]
-error = '''
-storage is not tikv
-'''
-
-["BR:PD:ErrPDInvalidResponse"]
-error = '''
-PD invalid response
-'''
-
-["BR:PD:ErrPDLeaderNotFound"]
-error = '''
-PD leader not found
-'''
-
-["BR:PD:ErrPDUpdateFailed"]
-error = '''
-failed to update PD
-'''
-
-["BR:PiTR:ErrPiTRInvalidCDCLogFormat"]
-error = '''
-invalid cdc log format
-'''
-
-["BR:Restore:ErrRestoreChecksumMismatch"]
-error = '''
-restore checksum mismatch
-'''
-
-["BR:Restore:ErrRestoreInvalidBackup"]
-error = '''
-invalid backup
-'''
-
-["BR:Restore:ErrRestoreInvalidRange"]
-error = '''
-invalid restore range
-'''
-
-["BR:Restore:ErrRestoreInvalidRewrite"]
-error = '''
-invalid rewrite rule
-'''
-
-["BR:Restore:ErrRestoreModeMismatch"]
-error = '''
-restore mode mismatch
-'''
-
-["BR:Restore:ErrRestoreNoPeer"]
-error = '''
-region does not have peer
-'''
-
-["BR:Restore:ErrRestoreRangeMismatch"]
-error = '''
-restore range mismatch
-'''
-
-["BR:Restore:ErrRestoreRejectStore"]
-error = '''
-failed to restore remove rejected store
-'''
-
-["BR:Restore:ErrRestoreResolvedTsConstrain"]
-error = '''
-resolved ts constrain violation
-'''
-
-["BR:Restore:ErrRestoreSchemaNotExists"]
-error = '''
-schema not exists
-'''
-
-["BR:Restore:ErrRestoreSplitFailed"]
-error = '''
-fail to split region
-'''
-
-["BR:Restore:ErrRestoreTableIDMismatch"]
-error = '''
-restore table ID mismatch
-'''
-
-["BR:Restore:ErrRestoreWriteAndIngest"]
-error = '''
-failed to write and ingest
-'''
-
-["BR:Restore:ErrUnsupportedSysTable"]
-error = '''
-the system table isn't supported for restoring yet
-'''
-
diff --git a/br/revive.toml b/br/revive.toml
deleted file mode 100644
index 4bcb5b8f035aa..0000000000000
--- a/br/revive.toml
+++ /dev/null
@@ -1,52 +0,0 @@
-severity = "error"
-ignoreGeneratedHeader = false
-confidence = 0.8
-errorCode = 1
-warningCode = 0
-
-[rule.blank-imports]
-[rule.context-as-argument]
-[rule.dot-imports]
-[rule.error-return]
-[rule.error-strings]
-[rule.error-naming]
-[rule.exported]
-[rule.if-return]
-[rule.var-naming]
-[rule.package-comments]
-[rule.range]
-[rule.receiver-naming]
-[rule.indent-error-flow]
-[rule.empty-block]
-[rule.superfluous-else]
-[rule.modifies-parameter]
-
-# Add these once issues are fixed
-[rule.confusing-naming]
-  severity = "warning"
-[rule.confusing-results]
-  severity = "warning"
-[rule.flag-parameter]
-  severity = "warning"
-
-# Currently this makes too much noise, but should add it in
-# and perhaps ignore it in a few files
-#[rule.unused-parameter]
-#  severity = "warning"
-#[rule.deep-exit]
-#  severity = "warning"
-
-
-# Already checked by megacheck
-# [rule.unreachable-code]
-
-# Adding these will slow down the linter
-# They are already provided by megacheck
-# [rule.unexported-return]
-# [rule.time-naming]
-# [rule.errorf]
-
-# Adding these will slow down the linter
-# Not sure if they are already provided by megacheck
-# [rule.var-declaration]
-# [rule.context-keys-type]
diff --git a/br/tidb-lightning.toml b/br/web/tidb-lightning.toml
similarity index 100%
rename from br/tidb-lightning.toml
rename to br/web/tidb-lightning.toml