Forum Discussion

Gossett's avatar
Gossett
Level 6
12 years ago

What is this error (what does it mean)? Screenshot attached

Topic:   I got it when cleaning out old backup sets
2012
Backup and Recovery
Backup Exec
Error messages
Training
Troubleshooting
  • David_Palmersto's avatar
    David_Palmersto
    12 years ago

    I see that you consider this solved for your case, but you may want to continue to investigate:

    1) This issue was much more frequent in builds before SP1a + first 2 hotfixes (189571 and 180964) + 1 newer one (194470), please make sure you run a LiveUpdate and have all 4 of those pieces installed.

    2) The issue can also come up if any of the media from the backup sets that you are deleting have been reused.  There is a known "window of opportunity" where BE2012 will re-use existing BKF files on disk storage instead of deleting them completely when DLM should.  If you are manually pruning ("deleting") backup sets, you can run into situations where BE attempts to delete a backup set that no longer exists - that can be the source of this error.

    Deleting those sets where BKF files have already been reused should not make the situation any worse (in fact, things should be better because now that old backup set does not point to the previously used BKF)..

    We have not seen any lasting problems created after receiving this error (except sometimes needing to restart the BE Management Service).

     

David_Palmersto's avatar
David_Palmersto
Level 4
12 years ago

I see that you consider this solved for your case, but you may want to continue to investigate:

1) This issue was much more frequent in builds before SP1a + first 2 hotfixes (189571 and 180964) + 1 newer one (194470), please make sure you run a LiveUpdate and have all 4 of those pieces installed.

2) The issue can also come up if any of the media from the backup sets that you are deleting have been reused.  There is a known "window of opportunity" where BE2012 will re-use existing BKF files on disk storage instead of deleting them completely when DLM should.  If you are manually pruning ("deleting") backup sets, you can run into situations where BE attempts to delete a backup set that no longer exists - that can be the source of this error.

Deleting those sets where BKF files have already been reused should not make the situation any worse (in fact, things should be better because now that old backup set does not point to the previously used BKF)..

We have not seen any lasting problems created after receiving this error (except sometimes needing to restart the BE Management Service).