# BR Limitations

__*BR restrictions*__

+ Unable to recover tables with charset=GBK to TiDB clusters prior to v5.4.0
+ Compatibility issues with backup and recover
  + Clustered index (tidb*enable*clustered_index)
  + New collation (new*collations*enabled*on*first_bootstra)
  + Global temporary tables (BR v5.3.0)
  + Version compatibility issues (check-requirements)
+ Data recover by BR cannot be synchronized to downstream via TiCDC or TiDB Binlog
  
-------------------------------------------------------------

scenario restrictions
BR does not support recover tables with charset=GBK before v5.4.0. Also, any version of BR does not support recover tables with charset=GBK to TiDB clusters prior to v5.4.0.
Ensure that the TIDB*enable*clustered_index global variable is the same during backup and recover, otherwise it will cause data inconsistencies, such as default not found and data index inconsistency.
Ensure that the new*collations*Enabled*on*star1first_bootstrap variable value of the cluster is the same as the one at the time of backup during recover, otherwise data index inconsistency and checksum failure
Be sure to use BR v5.3.0 and later version for backup and recover, as this will result in table definition errors for global temporary tables.

The built-in version of BR checks the TiDB cluster version against its own version before performing backup and recover operations. If the major versions do not match (for example, on BR v4.x and TiDB v5.x), BR will prompt you to abort. If you want to skip the version check, you can forcibly skip the version check by setting —check-requirements=false.

When BR recover data to an upstream cluster running TiCDC or TiDB Binlog, the recover data cannot be synchronized to the downstream cluster by the TiCDC or TiDB Binlog.