Migration Plan from Lower Version TiDB to Higher Version

This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: 低版本tidb迁移到高版本方案

| username: Mingdr

【TiDB Usage Environment】Production Environment
【TiDB Version】3.0.11
【Encountered Problem】Due to server performance issues and the outdated TiDB version, we are planning to set up another TiDB cluster for use. Now we want to migrate the old cluster to the new one. Are there any good solutions for non-stop (or minimal downtime) migration?
We initially planned to use TiCDC, but found that this tool is not available in the old version.

| username: Billmay表妹 | Original post link

Which version do you want to migrate to? Have you considered upgrading the original cluster without backing up the data?

| username: Billmay表妹 | Original post link

For cluster upgrades, you can consider: upgrading from 3.0 to 4 专栏 - 体验升级至4.0 | TiDB 社区

Then follow tiup to upgrade from 4.0 to 7.1.0

Cross-version cluster upgrade guide: 使用 TiUP 升级 TiDB | PingCAP 文档中心

| username: Mingdr | Original post link

We are preparing to migrate to 7.1. The original cluster and servers will no longer be used, so upgrading is not an option. As for backups, we will probably do it once.

| username: Hacker007 | Original post link

This is equivalent to rebuilding a new cluster, which is much simpler. Just synchronize the data to the new cluster, right?

| username: ffeenn | Original post link

It is still recommended to use incremental synchronization as the most robust method. Check the DM documentation
TiDB Data Migration Overview | PingCAP Documentation Center

| username: srstack | Original post link

If machine resources are sufficient, it is recommended to deploy a new high-version cluster and then fully synchronize the data. After stopping the upstream business and ensuring that the incremental data is fully synchronized, switch the business to the new machines. If machine resources are not sufficient, you can use tiup to gradually upgrade to the high version in small increments.

| username: 啦啦啦啦啦 | Original post link

DM is a tool for migrating MySQL to TiDB. Here, you can only use the TiDB Binlog (pump+drainer) method for synchronization and then use the cutover method to upgrade.
Refer to this link:

| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.