Rollback After TiDB Upgrade

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

Original topic: TiDB升级后回退

| username: TiDB_C罗

[TiDB Usage Environment] Production Environment / Testing / Poc
[TiDB Version]
[Reproduction Path] What operations were performed that caused the issue
[Encountered Issue: Issue Phenomenon and Impact]
[Resource Configuration]
The documentation clearly states that rollback after an upgrade is not supported.

However, in the video tutorial, it says rollback is possible. How can it be rolled back?

| username: zhanggame1 | Original post link

The question asks which one is incorrect. Obviously, d is correct, and c is incorrect.

| username: cassblanca | Original post link

Before upgrading, perform a full backup of the original cluster. If you need to roll back, use the backup files to overwrite. The official documentation does not currently provide a rollback plan or operation method.

| username: redgame | Original post link

Rollback is not supported after an upgrade.

| username: zhanggame1 | Original post link

Is there a tutorial for what you mentioned?

| username: ShawnYan | Original post link

Considering version compatibility, some versions do not support rollback. It is recommended to set up a new cluster for migration and upgrade, keeping the old version cluster as a rollback option.

| username: kavenab | Original post link

Production databases are generally not directly upgraded. Instead, a new cluster is set up and data is migrated. After adapting to the new version, the application is then moved to the new cluster.

| username: zhanggame1 | Original post link

It’s still not possible with large amounts of data or limited resources.

| username: tidb菜鸟一只 | Original post link

There is currently no direct rollback command.

| username: zhanggame1 | Original post link

Can we shut down the system, create a tar package of the tiup installation directory, as well as the software and data installation directories, for recovery purposes?

| username: kavenab | Original post link

Even hundreds of terabytes are upgraded in this way. We don’t lack hosts. If we really lack them, we can rent some cloud hosts for a day to transfer.

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

Theoretically possible, but practically impossible to do so. The downtime would be too long, and rolling back incremental data would be very difficult to handle.

| username: cassblanca | Original post link

It’s just file backup.

| username: TiDBer_vfJBUcxl | Original post link

I haven’t tried it, but I have seen a rollback plan [Quick Forced Rollback Plan When TiDB Upgrade Fails] 您的访问出错了

| username: cy6301567 | Original post link

Generally, they all upgrade.

| username: zhanggame1 | Original post link

If the data volume is only tens of gigabytes, it should be feasible to run it on an SSD.

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

:joy: Dozens of GB should not require TiDB, MySQL can handle it.

| username: zhanggame1 | Original post link

Innovation in development is essential, how can we use MySQL? Even though our data volume is small, we must use a domestic distributed database.

| username: system | Original post link

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