Media Not Being Purged- Manual Delete Error "Unable to Delete {0}"
Been having alot of issues since upgrading to Backup Exec 2012...One that is really getting on my nerves is my backup storage always running out of space. BE should be auto-purging the last backups to make room for new. Anyway, up until now I was going in and manually deleting backup sets older than 2 weeks. When I do that, I get the message about "dependant backup sets" which I always say "yes" to then I get multiple instances of "unable to delete {0}". I click "ok" on them (usually get it like 20x when deleting a few weeks of sets)
What is up with that error and how can I ensure that BE starts to auto-purge the old sets? My searches found little to nothing about my specific error but this article came up (http://www.symantec.com/docs/TECH187957 ) anyway implementing this registry change did nothing.
My Media is an eSata external mirrored 2 TB solution from HiRely. If I go to the media information it shows "Overwrite protected until: Infinite - Do not overwrite". It is greyed out without an option to change it. The media sets in the jobs show as between 14 and 7 days, depending on the type of backup I am running.
Anyone?
Before I scrap Backup Exec all-together and find a new solution? Been using it for quite a few years/versions and wouldn't mind staying on but this new build kind of sucks...also had a case open about P2Vs not working and support takes weeks to respond then just stops as they can't figure it out lol
Opened a support request and it turns out when my storage was originally setup it somehow got configured as a "disk cartridge". I had to go through hell-and-high-water to delete it; ended up deleting it through the SQL database. Anyway it should have been configured as "disk storage". So I don't see the "unable to delete {0} " messages anymore and if it doesn't prune old backups I'll report back as well as re-open my ticket with Symantec. Now on to figuring out why the job engine crashes every weekend on my full backups. yay.