[BackupSetIndex.init]@XXXXXX Index corrupted

Error

An error similar to [BackupSetIndex.init]@5749b290 Index corrupted ‘W:\backup-01.cybersecure.com.au\username\files\1297809059982’ occurs either during seeding, or during a local copy backup.

Cause

  1. This problem can occur as a result of too many files within the backup set.
  2. Some older versions had an issue when using the local copy backup feature.

Resolution

If the problem is seen during a seed copy or exchange backup:

  1. Reduce the amount of files within the backup sets – split them out into separate backup sets.
  2. For exchange backups, run more backups to commit/purge transaction logs more often.

If the problem is seen using the local copy backup feature:

  1. Upgrade the client software to the latest version
  2. Delete the .bdm files under the files/ folder on the local copy destination
  3. Decrypt the local copy into a separate location
  4. After the “Initializing decrypt action” has completed and it starts creating new folders and files, cancel the operation
  5. Delete any *.bdm.lck files under the files/ folder on the local copy destination
  6. Now that the .bdm database has been rebuilt the local backup should now work