GRT AD Backups - IMG media do not expire / get overwritten

[Eu-Tjin_Gan]

we recently implemented GRT AD backups. it's a cool feature that works fairly well. we created a B2D folder on a local disk and plan to back this up to tape. however, when we started scheduling the backups, we found that the IMG media do not expire or get overwritten.

we have tried all sorts of methods or settings, but none of them worked.
- setting maximum backup sets per B2D file
- disk space reservation for B2D
- set overwrite protection for media set to 1 day (as a test), but the IMG media still does not get overwritten.

looks like the IMG media is gonna grow until it fills up the local disk (which is crazy). we are currently trying to get a script in place to delete IMG images, which are older than the retention periods we intend to have (> 7days, etc.), but personally, this is silly, because retention periods and media expiration is an important part of backup policies :(

checked elsewhere in this forum and it looks like this is a bug (or something). am i right?? has anyone found a solution to this ... hotfix perhaps? thanks!

[Eu-Tjin_Gan]

apparently, this is an expected behaviour for GRT backups.

http://forums.symantec.com/discussions/thread.jspa?threadID=69675&tstart=45

i had a look at : http://seer.entsupport.symantec.com/docs/286794.htm

gonna try this out, let's see if it works.

[Sandy_Sandifer]

Hi,

Please read the following technote that explains how GRT backups work and what we recommend.
http://support.veritas.com/docs/286794

Thanks.

[kidputer]

The recommendations only delay the problem.
here is a fix that actually works:

If you cannot delete the media, eventually it will fill up the drive even if you partition it and even if it is large.
I just wasted a week of my life trying to make space on a drive, even reformatted the drive, still Disk full error.
Fianlly I just uninstalled the software and reinstalled it, recreated all my backups, and here is the key, I backed up my Backup exec database (the folder named "data").
When the backup disk gets full just reformat the drive and restore the database, presto, bug fixed.
Oh and don't forget to rename your catalog folder to catalog.old
BTW-I hope they fix this bug soooooon because it is a real headache and time waster.
The 3 day hold time indicates to me the entire world is stuck on this issue.