Many large "fake" backup sets exist in Deduplication folder

[LameDuck419]

I'm running Backup Exec 2012, fully patched, on Windows Server 2008 R2 Std x64. I have one 16.3TB deduplication storage folder. BE was upgraded from v2010 R3 about 6 weeks ago.

Today I was poking around in areas of the Backup Exec console that I hadn't seen yet, and came accross the page where I can view all backup sets in the dedupe folder (Storage tab -> Deduplication Storage Folder details -> Backup Sets). That's when I discovered that the oldest backup sets listed are those shown in the screen shot below - 'SHCBU1' is my media server:

There are 94 of these identical "backup sets" listed, totalling an obviously incorrect 418.3TB.

Why do these sets exist? Is it safe to delete them? Why or why not? As far as I know they didn't exist until I upgraded to 2012.

[lmosla]

Hello,

This issue may have been resolved by a past hot fix or service pack.  To reclaim space use the following document http://www.symantec.com/docs/TECH192557

[LameDuck419]

Thanks for the reply, I am familiar with the space reclamation process. Are you saying I should go ahead and delete the backups sets and then reclaim the space? From what I understand the reclamation process runs twice a day automatically, so I don't see how that would help unless I deleted the sets first...

[VJware · Accepted solution]

I guess, you are facing this cosmetic issue as outlined in http://www.symantec.com/business/support/index?page=content&id=TECH206200 This seems to be fixed in the next release of Backup Exec (BE2014)

[LameDuck419]

I suppose that is my issue... I was worried that it might be an indication of some other problem that may pop up down the road, but for now everything is running fine so I will ignore it. Thanks!

[LameDuck419]

I'd like to wait a couple more hours in case anyone else has any suggestions, otherwise I'll mark VJware's reply as the solution.

[LameDuck419]

I've decided to hold all backups, finish duplicating all backup sets to tape and then delete all backup sets in the deduplication storage folder (and maybe even the folder itself). During this process I discovered at least 3 other backup sets that show multiple copies that don't exist, so I believe VJware's solution is correct. It's just odd because the 4.45TB backup set from my first post never existed in the first place, so I have no idea why it would show up at all.