How to run a validation \ data integrity check on a backup set

Overview

A data integrity check (Rebuild Index) checks a backup set’s index files and repairs them. Run it when you see one of the errors listed at the bottom of this page. You can also run it to correct the storage size reported for a backup set.

Before you start

• The check can’t start while the backup set is running. Temporarily turn off the backup set’s schedule, so a backup doesn’t start during the check.
• The check can take a long time. How long depends on the number of files and folders in the backup set, the device’s disk and CPU speed, and whether other heavy jobs are running.

Run the data integrity check

1. Open the BOBcloud software on the device the backup set runs on.
2. Click Utilities.

   

3. Choose the backup set, then the backup destination.
4. Tick Rebuild Index only. The other options are for features we don’t use, and ticking them makes the check take much longer.
5. Click Start.

   

6. Wait for this message, which shows the check is complete.

   

7. Turn the backup schedule back on, and run the backup again.

If the problem persists

1. Close the BOBcloud software, including its icon in the system tray at the bottom right of the screen.
2. Find the backup set’s temporary folder: edit the backup set and click Show advanced settings → Others → Temporary Directory. The default is C:\Users\<username>\temp. Delete the contents of this folder.
3. Run the backup again.
4. If it still fails, change the Temporary Directory to a different folder, ideally on a drive with plenty of free space, and run the backup again.
5. If it still fails, raise a support ticket. Attach a screenshot of the data integrity check result and the logs described in Location of the BOBcloud Server and Desktop software logs.

Errors that need a data integrity check

Run a data integrity check if the backup log shows any of these errors.

Failed to initialize RemoteBDB.Cloud. Error=[BlockDBConfig.readConfig] unknown default path for creating new journal file config: 0

Unable to do Offsite backup, Error= [BlockDB.init] Error initializing bptree

See also Error initializing bptree.

Failed to initialize RemoteBDB.Cloud. Error=Fail to remove corrupted index

[BackupSetCmd.uploadBackupFiles][java.lang.RuntimeException] Error=[RuntimeException] [BackupFileIterator.Combined.hasNext] Throwable=[Bptree.KeyRangeIterator.hasNext] Error=[ABlock.parse] Cannot parse file

See also Bptree.KeyRangeIterator.hasNext: Cannot parse file.

Failed to initialize RemoteBDB.Cloud. Error=[SQLITE_ERROR] SQL error or missing database (table info already exists)

This last error has been reported since March 2020, when the index files changed from a flat-file format to an SQL database.