Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.Original topic: ticdc中断后很久，超过gc时间，如何恢复中间的数据
|
username: wfxxh
[TiDB Usage Environment] Production Environment
[TiDB Version] v5.4.3
TiCDC was interrupted for a long time before it was discovered, exceeding the GC time. How can I recover the data from the interruption point to the recent GC time to the downstream?
It cannot be restored, you can only redeploy the synchronization.
You need to start with a full backup, and then specify --start-ts to begin incremental backups, right?
If the backend can be redundant, you can directly specify a time.
It is used for database disaster recovery and cannot be redundant. TiCDC and TiDB Binlog seem to have very similar functions. Could you please explain the differences between the two in terms of usage?
There is no difference in usage, right? TiCDC executes more protocols and has better compatibility.
Yes, both CDC and binlog can achieve incremental data synchronization. Binlog was developed in the early stages of TiDB to be compatible with MySQL, while CDC was later developed specifically for TiDB. CDC has better adaptability to TiDB and offers stronger performance.
The binlog principle is the same as MySQL’s, and you can set the retention time. It has a higher fault tolerance rate and is slightly better than CDC for disaster recovery.
It depends on the version. Higher versions no longer support binlog…
TiCDC is officially developed specifically for TiDB, offering better performance and reliability.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: