Solved

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

Posted on 2014-11-27
6
1,100 Views
Last Modified: 2015-08-08
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
Comment
Question by:somicoy
  • 4
  • 2
6 Comments
 
LVL 5

Expert Comment

by:A Karelin
ID: 40475256
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
 

Author Comment

by:somicoy
ID: 40482377
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
 
LVL 5

Expert Comment

by:A Karelin
ID: 40482471
Do you have CASO server?
0
U.S. Department of Agriculture and Acronis Access

With the new era of mobile computing, smartphones and tablets, wireless communications and cloud services, the USDA sought to take advantage of a mobilized workforce and the blurring lines between personal and corporate computing resources.

 

Author Comment

by:somicoy
ID: 40482650
No,
the server is standalone installation of Backup Exec 2014.
0
 

Accepted Solution

by:
somicoy earned 0 total points
ID: 40913020
This issue solved itself when we purged the whole system and made a clean install.
No other solution was found.
0
 

Author Closing Comment

by:somicoy
ID: 40920564
No real solution to the issue was found.

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

Featured Post

Enterprise Mobility and BYOD For Dummies

Like “For Dummies” books, you can read this in whatever order you choose and learn about mobility and BYOD; and how to put a competitive mobile infrastructure in place. Developed for SMBs and large enterprises alike, you will find helpful use cases, planning, and implementation.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

By default, Carbonite Server Backup manages your encryption key for you using Advanced Encryption Standard (AES) 128-bit encryption. If you choose to manage your private encryption key, your backups will be encrypted using AES 256-bit encryption.
A Bare Metal Image backup allows for the restore of an entire system to a similar or dissimilar hardware. They are highly useful for migrations and disaster recovery. Bare Metal Image backups support Full and Incremental backups. Differential backup…
This tutorial will walk an individual through the process of configuring basic necessities in order to use the 2010 version of Data Protection Manager. These include storage, agents, and protection jobs. Launch Data Protection Manager from the deskt…
This tutorial will walk an individual through setting the global and backup job media overwrite and protection periods in Backup Exec 2012. Log onto the Backup Exec Central Administration Server. Examine the services. If all or most of them are stop…

756 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question