Restores fail for backups that used optimized duplication between Deduplication folders that span multiple media.
During an optimized duplicate operation in which the backups spans multiple media, Backup Exec incorrectly calculates the record number of the crossing object. The causes the restore operation to fail because it is looking in the wrong place for the data.
This issue has been resolved in Backup Exec 2010 R3 Service Pack 2
For existing backup sets, the following is a workaround:
1. Remove or rename the existing catalog for the backup set in question
2. Recatalog the backup set in question using the "slow" catalog function, as detailed in
3. Once this catalog operation has been completed, the restore can now be run.