Forum Discussion

euncit's avatar
euncit
Level 2
14 years ago

Backup Retention with backup-to-disk folders

We have setup the use of backup-to-disk folders in our setting. Someone else set this up and I am trying to figure out just how the retention policy works.

I see in the media set properties that I can specify an append period, but I don't see how I can say, only keep around 1 weeks worth, or so many backups, etc. Our diskspace is a bit challenged so I am needing to be able to say either of these options: I want to keep around so many backups for a folder or media set, etc, or to be able to say after so much time it is can be deleted.

How would I do this?

Any direction would be appreciated.

Sincerely,

Alan

  • Agree with Ken and partially with itsmeaffinity

    - set any jobs to disk targets as Overwrite on start

    - Set your media set Overwrite protection to 1 week - or 6.5 days (in hours) if you want to overwrite on the exact anniversary of 1 week

    However would recommend not using the Infinite Append option on your media set - yes setting the jobs to start as oevrwrite only kind of ignores that setting, however if you run a one off backup job, or another admin creates a job and a Append job is accidentally created then it will mess up the timings. So would suggest putting some form of limit on the append period (even 0 hours) as well.

  • Hi

    First thing is you need to go to media tab & in there select the media set used by you to do backup & when you right click on it select overwrite protection like for 1 week if you want to protect data for 1 week or so on so after 1 week data will be overwritten & select appen as allow infinite append

    Now after doing that go to tool-option-meida management & select option called partial & then select the option called overwrite recyclable media & then overiwrite scratcgh media so by using this option once after 7 days file are set to be overwritten backup exec can overwrite those file intead of making new bkf file

    Finally in backup job select the media set which have configured by going to device & media

    Hope this helps

  • For Disk based backups, I would recommend the you do NOT use append, but rather specify Overwrite only. Agree that option to "Use overwriteable media in the target media set before scratch media" should be selected

  • Agree with Ken and partially with itsmeaffinity

    - set any jobs to disk targets as Overwrite on start

    - Set your media set Overwrite protection to 1 week - or 6.5 days (in hours) if you want to overwrite on the exact anniversary of 1 week

    However would recommend not using the Infinite Append option on your media set - yes setting the jobs to start as oevrwrite only kind of ignores that setting, however if you run a one off backup job, or another admin creates a job and a Append job is accidentally created then it will mess up the timings. So would suggest putting some form of limit on the append period (even 0 hours) as well.

  • I just wanted to give a final update on what I did now that it has been in operation for a while and I am seeing my overwrites working.

    Backup-to-Disk folders I have set to 20 or 30 GB (though this could be set at anything, it looks like- just creates more files). I leave the same amount of space required as one of these backups.

     

    For media - I am doing an overwrite protection for the number of weeks I want to keep things around and have an append period of 0 hours.

    I had left the default of the "Full - protect allocated and imported media"

    and

    "Overwrite scratch media before overwriting recyclable media".

    This has worked fine, but as I think about it, probably would be best to at minimum change the latter.

    Thanks for all of your help!

    Alan

  • "Overwrite scratch media before overwriting recyclable media".

    This has worked fine, but as I think about it, probably would be best to at minimum change the latter.

    If you leave this as is, BE will continue to create new BKF files until either the disk is full or the reserve has been met.  If you have a dedicated volume for B2D, this shouldn't matter a whole bunch, just be aware that you will eventually have 0 free space, so don't panic when it happens wink