Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.
Original topic: TiDB热备份的原理是什么？是否和Oracle RMAN类似？
【TiDB Usage Environment】Production\Test Environment\POC
【TiDB Version】
【Encountered Issues】
【Reproduction Path】What operations were performed to cause the issue
【Issue Phenomenon and Impact】
【TiDB Operator Version】：
【K8s Version】：
【Attachments】：
TiDB uses multiple replicas by default and ensures real-time and consistency through the Raft protocol, which is quite different from Oracle…
Completely different. The datafile backed up by Oracle RMAN is inconsistent; the CHECKPOINT_CHANGE# value at the head of each datafile may not be equal. Recovery requires rolling forward through archived logs or even redo logs to restore to the same SCN point before it can be opened. TiDB’s hot backup BR tool is based on the MVCC snapshot at the SI isolation level, and the SST files backed up from each TiKV are consistent.
The backup from RMAN is the original physical data file, while the backup from BR generates new SST files.
So SST files are essentially still logical backups?
Physical backup is equivalent to reading out the snapshot data at the backup_ts timestamp and generating new SST files. You can refer to the following article:
This topic will be automatically closed 60 days after the last reply. No new replies are allowed.
|
username: alfred
|
username: 
|
username: 
|
username: 
|
username: