How do you verify the integrity of the FULL BACKUP?
In this article, we are going to discuss BACKUP validation.
Each backup has a checksum associated with the files that comprise the backup. Each checksum is a long string of hex characters, with every eight characters representing a subsection of the backup. To create this checksum, SingleStoreDB utilizes CRC32C, a common variant of CRC32, to process the backup files.
When taking a backup, Singlestore performs no validation of full backups. To perform validation of a full or split backup, Singlestore offers a Python script that is based on the CRC32C checksum.
Note: Validation completion time depends on the backup size and may take hours.
If you are using Toolbox for managing backups, you can use the Toolbox command sdb-admin validate-backup. One of the benefits of using the toolbox command is that this tool can verify full and even incremental backups (compared to the Python script that verifies full backups only).
Validate checksum (applicable for full backups only):
sdb-admin validate-backup -r file://foo/bar backup1 --full-checksum
Validate a specific version of incremental backup, for example,
backup1 with an incremental ID 1:
sdb-admin validate-backup -r file://foo/bar backup1 --incr-backup-id 1
You can find more on this topic and the mentioned Python script in our docs: