Forum Discussion

Xuanpv's avatar
Xuanpv
Level 3
12 years ago

Full Hard disk, need delete something old backup files.

Dear all.

I'm implementation system with 10  VM window server2003/2008. I'm installing  BE 12.5 on 01 VM Window server  . set backup system state & C: Drive 

Backup from Mon-Sat is differentials , Full at Sunday . backup to D drive (D:\ drive 1TB mapping from storage) .

After over 01 week  the D:\Driver is full, I testing the backup file increate over 70GB for every 01 day . Now i need solution delete or setting to get space at D:\drive , i want backup file only 500 GB ?

Have you got any solution for this case ? pls advise

Thanks !

XuanP

17 Replies

  • Hello, From screenshot its clear tat its backup exec 2012...data life cycle management has been introduced in it which runs automatically and it should delete expired backup sets automatically....the reason backup sets are not getting deleted automatically is because of the backup sets...backup exec now keeps a track of type of data..thus as you have differentials running every day and full schedule for Sunday backup exec won't delete any of this backup until next full backup.... So if you have set up job in such way that data should be protected for a week and last differential backup is schedule for Saturday than data will be protected for 2 weeks until the last differential backup set expires...... To overcome this ....setup overwrite protection for a day for full and diffrential to 12 hours... This time u might have to manually delete sets however next rotation onwards it should be fine.... Please mark this as solution if this answers your question and resolves your issue.
  • There is no over.write protection and append period in Backup Exec 2012 in the backups are targeted to Disk based storage.

    Data Life Cycle management is a feature which will groom the backup set once they are expired

    Grooming means deleting the backup sets from the actual locatio

    So if you backup 70 GB everyday and it will fill 490 GB in 7 days

    on the 8th day you want BE to groom the 1st day`s backup set in order for the space to never cross that 500 GB mark

    For this

    Create a backup job and in the storage tab select keep the backup for 7 days

    and on the 8th day it will delete the 1st days backup set

    Now this is how it is suppose to work, however BE has some DLM feature related issue which is fixed with the new SP2 release

    Before anything go ahead and install the

    Backup Exec 2012 revision 1798 Service Pack 2

    and this should take care of the problem you are encountering.

     

  • Kunal how does it work in this scenario Sunday full Monday to saturday incremental With option selected to keep backup for 5 days..thus this means it should delete full... There was an enhancement in backup exec 2012 in above example it would still protect full because incrementals are still not expired because now in BE it keeps bakups as sets.....
  • About the data lifecycle management grooming process · Data lifecycle management checks for expired backup sets and then grooms those backup sets and the associated backup data to free disk space. · Data lifecycle management runs every 4 hours and whenever a low disk storage alert is received. · Data lifecycle management checks the dependency between the full and the associated incremental or differential backup sets to prevent breaking a chain of full/incremental or full/differential backup sets. Data lifecycle management does not groom expired full and incremental backup sets if there is a dependent incremental backup set that has not expired. · Data lifecycle management does not delete the last copy of the latest recovery point chain. A recovery point chain is the associated full and incremental backup sets that are generated from the same job for the same resource using the same selection list, for example, \\Server\C:, \\Server\MSSQL\BEDB). These are the backup sets that are required to successfully recover a resource to the latest point-in-time. Please have a look at the article below which has this info http://www.symantec.com/docs/TECH201826
  • When you keep data for 7 days, you would end up with 8 backup sets because when the job on the 8th day runs, the backup set from the first day is still protected.

  • Which means that the entire chain would still be retained when the new backup chain starts and the 500GB limit would be busted.