Backup Exec seeing dependencies that don't exist
We have a new client using Backup Exec set up to delete old backup sets as space is needed.
The problem they seem to be having is that Backup Exec is deleting the old backup set from the disk correctly, but emails "Error E98F0038: Specified object cannot be removed as dependency exist" and does NOT remove the deleted set from its recovery points list in Manage Backup Destination.
I'll say here that there are no dependencies because there are no incremental backups, they're all full backups.
When we go into Manage Backup Destination BE immediately indicates that files are missing for certain sets and do we want to delete them, when we delete them all is well. However, we have to manually go in and do so every day. If we don't, the next time around BE seems to use its list of backup recovery points (still containing the old / deleted sets) to determine what disk space is left, rather than simply checking the actual disk space. It then deletes 2 or 3 sets (1 or 2 too many!) instead of just one.
Does anyone konw what might be causing BE to think there are dependencies?