OceanBase Database provides rich features to protect data so that it remains secure, reliable, and free from loss or corruption in various human or non-human error scenarios. These features include multi-replica replication for high availability (HA), recycle bin, flashback query, and backup and restore.
Hardware exceptions
When a disk becomes faulty, the data stored on the disk may encounter errors. In OceanBase Database, checksums are stored for redo logs and SSTable data. When data is read, strict checksum verification is performed to detect errors in a timely manner. The mechanism that detects silent data corruption can also detect errors in cold blocks that have not been read for a long period of time. For more information about the mechanism, see Detect silent data corruption.
When a network device such as a switch becomes faulty, a packet error may occur. Strict packet verification and check are performed for all network packets that are exchanged between clients and OBServer nodes and within the OceanBase clusters.
Manual exceptions
Database objects that are deleted by mistake can be restored from the recycle bin.
When an application has a software defect, or an operation error or malicious attack occurs, table data may be modified to incorrect data. You can use the flashback query feature to read historical snapshots of table data and restore the correct data.
OceanBase Database also provides backup and restore, which offers an efficient mechanism for backing up all data and metadata. It is the most reliable way to protect user data. For more information about backup and restore, see Backup and restore.