The Issue is fixed in Backup Exec 21.2 . With this fix installed the newer sets when they get deleted/expired, it will remove the catalog files from the Managed Backup Exec server as well.

The catalogs of backup sets prior to patch installation where this issue is evident will need to be manually cleared.

The manual process involves first making sure that the set and all its dependants are expired. Since these are sets whose catalog file is only present and not the media ( as catalog and media are deleted from the server where backup and duplicate ran but a catalog xml which gets copied to the target server which was the destination of the duplicate job is still present and causing the set to show up in the console), you can make a note of catalog file names of such sets. The way you can do it is by going to details of the Backup Set and checking the catalog file name. To ensure the set is not visible in the BE console the services can be stopped on both CAS and MBES ( showing that set ) and then those catalog file names can be moved out ( not copied out). When all those catalog files ( which do not have a media associated with it ) are removed then start all BE services and those ( sets without media associated with them) shoud not be visible. Make sure to search and remove the catalog files from both CAS and MBES server. This steps is helpful only if the Issue matches to this completely else if a set has a valid media associated with it then the set is only showing expired and actual cause of why it is not deleting even after showing expired has to be investigated. Also one need to ensure that the problem explained in this article gets solved for the newer backup sets after applying the patch or upgrading to newer release after Backup Exec 21.2

Note: It is recommended that the Patch be installed on Central Administration Server and then on the Managed Backup Exec Server.

In a CAS MBES environment where duplication is happening between the managed backup exec server and MBES are set to use Replicated or Distributed Catalog mode, the catalog entries for the Duplicate set do not get deleted from the Managed Backup Exec Server hosting the Disk Device where the duplicate job is targetted to.

Example Scenario :

1 CAS
MBES1 and MBES2

Backup Job runs on MBES1 and then duplicates to shared disk device hosted on MBES2.
Catalog files x.fh and x.xml are created for Primary set which got backed up to the device hosted on MBES1
Catalog files y.fh and y.xml are created for Duplicate Set which got duplicate to shared device hosted on MBES2

Note : For Replicated mode x (fh and xml) and y (fh and xml) will get copied on CAS and for the duplicate set, y.xml will get copied on the MBES2 whose device is being used for the duplicate copy.

When Primary Backup Set expires DLM deletes the media and catalog from the MBES and CAS.
When the Duplicate Backup Set expires, the Catalog entries on MBES and CAS for that set are deleted along with Media used by the Duplicate Set (from the device hosted on MBES2) but the y.xml (copied on the MBES2) remains on Catalog folder.

When the Backup Set is viewed from the Device hosted on MBES2, these expired sets still show up in the UI.

ETrack: 3850963 ETrack: 3958694