3、主生产中心故障时，会有秒级的数据无法同步，数据一致性无法 100% 保障（RPO > 0） 4、主生产中心故障时，需手动切换业务 MySQL 没有原生的安全的同步方案 NewSQL | TiDB 简单配置即可保障所有的数据中心 100% 同步，真正意义上的多活 完全实现 国标（信息安全技术-信息系统灾难恢复规范GBT 20988-2007 ）最高等级 第六级的要求（RTO = 0，RPO = 0） NewSQL - 大数据量下高压力实时处理的完美解决方案

在以下缺点：资源利⽤率低、维护成本⾼、RTO (Recovery Time Objective) 及 RPO (Recovery Point Objective) ⽆法真实达到企业所期望的值。TiDB 采⽤多副本 + Multi-Raft 协议 的⽅式将数据调度到不同的机房、机架、机器，当部分机器出现故障时系统可⾃动进⾏切换，确保系统的 RTO <= 30s 及 RPO = 0。 对存储容量、可扩展性、并发要求较⾼的海量数据及⾼并发的

facility Mission-1 nearing final integration for March 2024 launch Relative navigation testing on RPO testbed [Sept 2023]atomosspace.com | 5 • Understanding the past • Investigating the new patterns

schedule data to different data centers, racks, and machines, ensuring system RTO ￿ 30 seconds and RPO = 0. • Massive data and high concurrency scenarios Traditional standalone databases cannot meet the following key capabilities: • Replicating incremental data between TiDB clusters with second-level RPO and minute-level RTO. • Bidirectional replication between TiDB clusters, allowing the creation of and the replication lag is small. It allows data loss of 10s at most, that is, RTO <= 5 min, and P95 RPO <= 10s. TiCDC replication lag increases in the following scenarios: • The TPS increases significantly

schedule data to different data centers, racks, and machines, ensuring system RTO ￿ 30 seconds and RPO = 0. • Massive data and high concurrency scenarios Traditional standalone databases cannot meet the satisfies the following requirements: • Back up cluster data to a disaster recovery (DR) system with an RPO as short as 5 minutes, reducing data loss in disaster scenarios. • Handle the cases of misoperations last refresh every 3-5 minutes to the backup storage, which can achieve a Recovery Point Objective (RPO) as short as five minutes. 904 8.4.1.3.2 Restore backup data Corresponding to the backup features

schedule data to different data centers, racks, and machines, ensuring system RTO ￿ 30 seconds and RPO = 0. • Massive data and high concurrency scenarios Traditional standalone databases cannot meet the satisfies the following requirements: • Back up cluster data to a disaster recovery (DR) system with an RPO as short as 5 minutes, reducing data loss in disaster scenarios. • Handle the cases of misoperations last refresh every 3-5 minutes to the backup storage, which can achieve a Recovery Point Objective (RPO) as short as five minutes. 908 8.4.1.3.2 Restore backup data Corresponding to the backup features

schedule data to different data centers, racks, and machines, ensuring system RTO ￿ 30 seconds and RPO = 0. • Massive data and high concurrency scenarios Traditional standalone databases cannot meet the satisfies the following requirements: • Back up cluster data to a disaster recovery (DR) system with an RPO as short as 5 minutes, reducing data loss in disaster scenarios. • Handle the cases of misoperations last refresh every 3-5 minutes to the backup storage, which can achieve a Recovery Point Objective (RPO) as short as five minutes. 8.4.1.3.2 Restore backup data Corresponding to the backup features, you

schedule data to different data centers, racks, and machines, ensuring system RTO ￿ 30 seconds and RPO = 0. • Massive data and high concurrency scenarios Traditional standalone databases cannot meet the satisfies the following requirements: • Back up cluster data to a disaster recovery (DR) system with an RPO as short as 5 minutes, reducing data loss in disaster scenarios. • Handle the cases of misoperations last refresh every 3-5 minutes to the backup storage, which can achieve a Recovery Point Objective (RPO) as short as five minutes. 902 8.4.1.3.2 Restore backup data Corresponding to the backup features

性、容灾要求较高。传统的解决方案的资源利用 率低，维护成本高。TiDB 采用多副本 + Multi-Raft 协议的方式将数据调度到不同的机房、机架、机器，确 保系统的 RTO <= 30s 及 RPO = 0。 33 • 海量数据及高并发的 OLTP 场景 传统的单机数据库无法满足因数据爆炸性的增长对数据库的容量要求。TiDB 是一种性价比高的解决方 案，采用计算、存储分离的架构，可对计算、存储分别进行扩缩容，计算最大支持 重的自然灾害，提供业务误操作 “复 原” 的能力。 TiDB 备份恢复功能可以用于满足以下业务的需求： • 备份集群数据到灾备系统，并保证 Recovery Point Objective (RPO) 低至 5 分钟，减少灾难场景下数据的丢失。 • 处理业务数据写错的案例，提供业务操作的 “复原” 能力。 • 审计业务的历史数据，满足司法审查的需求。 • 复制 (Clone) 生产环境， MB/s，备份速度具有可扩展性；更详细说明 请参考备份性能和影响。 • 单独运行日志备份时影响约在 5%。日志备份每隔 3 ～ 5 分钟将上次刷新后产生的变更数据记录刷新到 备份存储中，可以实现低至五分钟 RPO 的集群容灾目标。 8.4.1.3.2 恢复备份数据 与备份功能相对应，你可以进行两种类型的恢复：全量恢复和 PITR。 • 恢复某个全量备份 – 恢复集群快照数据备份：你可以在一个空集群或不存在数据冲突（相同

性、容灾要求较高。传统的解决方案的资源利用 率低，维护成本高。TiDB 采用多副本 + Multi-Raft 协议的方式将数据调度到不同的机房、机架、机器，确 保系统的 RTO <= 30s 及 RPO = 0。 34 • 海量数据及高并发的 OLTP 场景 传统的单机数据库无法满足因数据爆炸性的增长对数据库的容量要求。TiDB 是一种性价比高的解决方 案，采用计算、存储分离的架构，可对计算、存储分别进行扩缩容，计算最大支持 重的自然灾害，提供业务误操作 “复 原” 的能力。 TiDB 备份恢复功能可以用于满足以下业务的需求： • 备份集群数据到灾备系统，并保证 Recovery Point Objective (RPO) 低至 5 分钟，减少灾难场景下数据的丢失。 699 • 处理业务数据写错的案例，提供业务操作的 “复原” 能力。 • 审计业务的历史数据，满足司法审查的需求。 • 复制 (Clone) MB/s，备份速度具有可扩展性；更详细说明 请参考备份性能和影响。 • 单独运行日志备份时影响约在 5%。日志备份每隔 3 ～ 5 分钟将上次刷新后产生的变更数据记录刷新到 备份存储中，可以实现低至五分钟 RPO 的集群容灾目标。 8.4.1.3.2 恢复备份数据 与备份功能相对应，你可以进行两种类型的恢复：全量恢复和 PITR。 • 恢复某个全量备份 – 恢复集群快照数据备份：你可以在一个空集群或不存在数据冲突（相同