10-13-2014 10:52 PM
My question is why Backup Exec always deletes expired disk backup datasets, even when it's not necessary because there is free space available on the same disk? I wanted to have as many copies as possible and this behavior prevents it. I am using Backup Exec 2012 version 14.0 Rev.1798 (64-bit) Thanks for your help
Solved! Go to Solution.
10-15-2014 12:23 AM
10-15-2014 12:40 AM
No, it isn't bad design. Every backup application on the market has retention times, and doesn't offer the ability to "think for itself" and simply increase that to fill up disk space.
pkh's advice is correct...it would be correct for Veeam, ARCserv etc.
Thanks!
10-14-2014 07:15 PM
This is by design. DLM will groom backup sets that has expired. See the blog and my article below on how your backup sets are managed.
https://www-secure.symantec.com/connect/fr/blogs/data-lifecycle-management-be-2012
https://www-secure.symantec.com/connect/articles/when-backup-sets-are-deleted-under-dlm
If you want to retain more copies of your backups then you need to increase the retention period.
10-15-2014 12:03 AM
IMHO this is a bad design decision. I want to have as many disk backups as possible, by using all the available space. Of course, when there is no more space available for a new backup, then BE must delete the expired data sets, but no before.
10-15-2014 12:23 AM
10-15-2014 12:40 AM
No, it isn't bad design. Every backup application on the market has retention times, and doesn't offer the ability to "think for itself" and simply increase that to fill up disk space.
pkh's advice is correct...it would be correct for Veeam, ARCserv etc.
Thanks!
10-15-2014 03:48 AM
It is possible to have as many as possible, just count it out by yourself and increase the retention accordingly. Backup exec has no artificial intelligence to predict how much backup sets it can keep on disk...
10-31-2014 12:52 AM
Thanks for your replies!
10-31-2014 12:54 AM
No problems!