Backup Exec 21.4 or 22 may not delete OST media and cause the Deduplication Storage to fill up

Problem

Backup Exec 21.4 or 22 may not delete OST media and cause the Deduplication Storage to fill up

Error Message

Backup Exec 21.4 Adamm.log from a Backup Exec server whose Deduplication Storage is not releasing space.  Backup Exec Adamm.log is located by Default (C:\Program Fles\Veritas\Backup Exec\Logs) folder.
 

DeviceIo: ostutil:TruncateImage BEOST_00010466 could not be deleted because of error -1
Quarantine incomplete OST image OST00010466-4A9130B5709D33BB - ERROR = 0x0000001F (ERROR_GEN_FAILURE)
DeviceIo: ostutil: DeleteOstImage, timeout BEOST_00010451
DeviceIo: ostutil:TruncateImage BEOST_00010451 could not be deleted because of error -1
Quarantine incomplete OST image OST00010451-4A9130B5709D33BB - ERROR = 0x0000001F (ERROR_GEN_FAILURE)

Adamm.log from a Backup Exec 22 media server whose Deduplication Storage is not releasing space
 

DeviceIo: ostutil: PureDisk:BKPSerV duplicate entry 3429
DeviceIo: ostutil: PureDisk:BKPSerV duplicate entry 3562
DeviceIo: ostutil: PureDisk:BKPSerV duplicate entry 3566
DeviceIo: ostutil: PureDisk:BKPSerV duplicate entry 3368

Cause

Affected Configuration - The problem is only seen in a Central Administration Server (CAS) and Managed Backup Exec Server (MBES) type of environments. (Except Scenario 3)

Scenario 1

CAS and MBES have Deduplication Storage configured.
MBES Deduplication Storage is shared with CAS
Backup Jobs are configured on CAS and run on it to CAS Deduplication Storage and then duplicated to MBES Deduplication Storage which shows up on CAS as well (since it is shared with CAS)

In this scenario, DataLifeCycle Management (DLM) deletes the Backup set from MBES Dedupe storage (sets which has expired) but does not remove the OST media associated with that Backup set. This causes the media to
accumalate and in turn the storage consumption continues to increase. The issue only affects non GRT backup sets.

Scenario 2

CAS and MBES have Deduplication Storage configured.
CAS Deduplication Storage is shared with MBES
Backup is run from CAS but delegated to run on MBES and use the MBES Deduplication Storage.
Then the same job duplicates the set to CAS Deduplication storage (The duplicate job runs on MBES)

In this scenario, DataLifeCycle Management (DLM) deletes the Backup set from CAS Dedupe storage when the 
set expires but does not remove the OST media associated with that Backup set. This causes the media to acumulate and in turn the storage consumption continues to increase. The issue only affects non GRT backups sets.

Scenario 3

Standalone Backup Exec Server configured with Deduplication Storage and Deduplication enabled Cloud Storage.
Backup is done to Local Dedupe Storage and then Duplicated to Cloud Deduplication Storage 
When the backup set on Cloud Deduplication Storage expires it deletes the set info from console but the OST media are still left behind in the Cloud Deduplication Storage. 
 

Solution
 

There are no plans to address this issue by way of a patch or hotfix in earlier versions of the software at the present time.  However, the issue has been addressed in the revision of the product specified at the end of this article. 
 
Please contact your Veritas Sales representative or the Veritas Sales group for upgrade information including upgrade eligibility to the release containing the resolution for this issue.

This issue is resolved in Backup Exec 22.1.