Backup verification for OceanBase Database primarily addresses the integrity and correctness of backup and archive data. Users can proactively verify for issues like missing files, physical data damage, and logical inconsistencies in backup sets and archived logs without performing a restore operation.
You can verify the backup based on verification levels. The backup verification consists of the basic verification and physical verification.
Basic verification: Only checks the completeness of the file list.
Physical check: Check the correctness and logical consistency of physical data.
Features
The backup verification feature of OceanBase Database has the following characteristics:
Increase the success rate of the restore: By preverifying, you ensure you're prepared for any situation.
Hierarchical validation capabilities: Provides two verification levels—Basic and Physical—to accommodate different requirements for verification timeliness and depth.
Supports flexible validation of backup and archive paths: You can validate the entire backup and archive path, a specified backup set, and a specified log archive piece. Additionally, you can cross-cluster validate the backup data in a specified path.
Use Cases
Backup verification is typically used in the following scenarios:
Integrity Check of Data Migration: After data is copied between directories or storage media, ensure there are no missing files.
Backup set availability check: Check whether the backup set supports the restore operation without performing the restore operation.
The following table describes the recommended verification methods in common business scenarios, based on the verification levels and granularities in OceanBase Database.
| Use case | Recommended validation scheme | Reference document | -------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------- | ------------------ | |
|---|---|---|---|---|---|---|
| Scheduled backup checks: Check whether backup sets generated by the current tenant are available. | Perform physical-level verification to check the entire backup and archive path. | Verify the backup and archive paths | ||||
| Backup after data migration: After the backup data is copied, only used for quick confirmation of whether the files are complete | Specify the backup set to verify the basic-level verification on the specified path. | Verify the backup set or archive piece at the specified destination | ||||
| Precautions for remote restore: Perform the remote restore task for the backup data of Cluster A to verify its availability on Cluster B. | Verify the backup data using the specified path. | Validate the backup set or archive piece on the specified path | ||||
| Verify specific backup data using sampling or quick validation: verifies only the most recent full backup. | Verifies a specified backup set by specifying backup_set_id. |
Verify a specified backup set or log archive piece |