Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1621
  • Last Modified:

How to purge old, expired and 'nonexistent' backup sets in Symantec Backup Exec 2014

We upgrade our Backup Exec 2012 to 2014 and after that I have not been able to figure out how to remove old backup sets.

Backup Sets that are associated with known media can be removed by 'expiring them'. However Backup Sets that do not have know media (storage status: Unknown) wont get removed even though they are Expired.

Some of these old Backup Sets are remnants from years away (failed and temporary medias) and they are never coming back. In Backup Exec 2012 I could manually remove these Backup sets one by one. Is there a way to achieve the same with Backup Exec 2014?

Here's a screenshot to illustrate the issue.

Expired backups in Backup Exec 2014
0
somicoy
Asked:
somicoy
  • 4
  • 2
1 Solution
 
A KarelinCommented:
Hi,
Install the latest updates http://www.symantec.com/business/support/index?page=content&id=TECH66724
Also check Configuration and Settings - Backup Exec Settings - Storage - Allow Backup Exec to delete all expired backup sets
0
 
somicoyAuthor Commented:
Thank you A Karelin.

Media server is at it's newest version and hotfixes were applied during upgrade. The 'Allow Backup Exec to delete all expired backup sets '- option is also in use and seems to be working for backup sets that are associated with some known media.
0
 
A KarelinCommented:
Do you have CASO server?
0
NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

 
somicoyAuthor Commented:
No,
the server is standalone installation of Backup Exec 2014.
0
 
somicoyAuthor Commented:
This issue solved itself when we purged the whole system and made a clean install.
No other solution was found.
0
 
somicoyAuthor Commented:
No real solution to the issue was found.

The workaround was to make a clean install using new SQL instance.
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now