RuntimeException errors on BOBcloud Server OBM 7

1

Error

You might experience these errors on BOBcloud Server backups using Ahsay OBM 7

[erro] [BlockDB.init][BlockFileCorruptedExpt] Error initializing bptree, \Predefined-backup-id\index\index.b2b, Error=[BlockFile.commitFromJournal] Failed to commit journal, caused by [g] [BlockFile.commitFromJournal] Failed to commit journal, caused by [RuntimeException] [CommitJournal.run] error, caused by [f] [BlockFile.saveForJournal] Not all data can be written to blocks available

[cbs] erro,"[g] [BlockDB.init][BlockFileCorruptedExpt] Error initializing bptree, \Predefined-backup-id\index\index.b2b, Error=[BlockFile.commitFromJournal] Failed to commit journal, caused by [g] [BlockFile.commitFromJournal] Failed to commit journal, caused by [RuntimeException] [CommitJournal.run] error, caused by [f] [BlockFile.saveForJournal] Not all data can be written to blocks available",0,0,0,

[cbs] end,BS_STOP_SUCCESS_WITH_ERROR,0,0,0,

Cause

Prior to OBM v7.13.0.2 the CRC check would was not able to fix a corrupted index file in the same way version 6 could.
This was fixed in v7.13.0.2

Fix

Upgrade CBS (system providers only) and BOBcloud Server \ OBM 7 to version v7.13.0.2

For existing backups which have successful backed up previously, rebuild the index as follows:

  1. Close the BOBcloud \ Ahsay OBM interface
  2. Stop the BOBcloud \ OBM service (this is server services)
  3. Add com.ahsay.cloudbacko.core.bset.file.RemoteBDB.forceRebuild=true in ‘C:\Program Files\serverbackup\cb.opt’
    You will notice the name cloudbacko. This is Ahsay’s company name for their hosted Ahsay
  4. Restart the BOBcloud \ AhsayOBM interface and service (this is server services)
  5. Run the backup once
  6. After the backup has finished, close the BOBcloud \ Ahsay OBM interface.
    Remove the true command added in step 3. If this isn’t removed the next backup job will rebuild the index again
  7. Run the backup again to verify the issue is solved

Ahsay OBM version 7