Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.Original topic: TiDB双机房灾备建设是否有TiCDC base方案
|
username: TiDBer_yyy
The official documentation is quite outdated, from June 2020, and it provides a binlog-based solution. I would like to ask if there is an official TiCDC-based solution available.
It is basically the same as the binlog base solution, just replace TiDB-Binlog with TiCDC, as the two overlap in functionality.
The specific solution depends on how you implement it with components. TiCDC can perform cross-data center backups, and that’s how we do it.
For local disaster recovery, we are currently using fiber optics for strong synchronization. For remote locations, we can only do asynchronous synchronization.
How do you perform data validation?
Data validation for TiDB master-slave cluster will check and obtain upstream and downstream timestamps.
|
username: 
|
username: 
|
username: 
|
username: select * from tidb_binlog.checkpoint;
Does ticdc check the checkpoint-ts timestamp?
"status": {
"resolved-ts": 419036036249681921,
"checkpoint-ts": 419036036249681921,
"admin-job-type": 0
},
Is it a plan for two centers in the same city with four replicas for disaster recovery?
We want one of the three replicas to be a local replica, if the network allows.
Add the configuration items --sync-point and --sync-interval to the changefeed in TiCDC to obtain the associated TSO of the upstream and downstream.
This topic was automatically closed 1 minute after the last reply. No new replies are allowed.
|
username: 
|
username: