Number of Backups to Retain?
I'm nearing the completion date of my trial version of TI2014 and am looking at purchasing it. A couple of questions:
- Is there a way in the program to tell it how may backup copies you want to retain and have it automatically delete the oldest backup when it exceed that number - my previous backup program allowed you to set the number to retain and it managed that.
- It appears that the backup copy name is the same for all backups and it just inserts the "Date Modified" to outline different backups? Is this true or am I missing something in having the actual date inserted in the backup filename as was allowed in other backup program (that is, without having to create a new backup procedure each backup)?
Thanks for any insights.
Charlie
I looked at the items you included, but where does it tell you how to tell the backup scheme how many backups to retain? I want to retain just the 2 most recent backups and have it delete the older one when I create a new backup. How, in simple terms, do I set the backup scheme to do that automatically do that?
You have not indicated the type of backups you intend to make as I discussed in my prior posting. Depending upon whether you want full only (11-full); or full plus incremental(11-Inc); or full plus differential (11-Dif) will control what settings you use in your "backup scheme".
As you have not mentioned incremental of differential type backups, I will assume for this example, that you wish to create only full type backups so each full backup would equal 1 recent version chain. (
Figure 11-Full: Example of custom/full backup method settings These automatic cleanup settings will provide for automatic deletion of the oldest backups after the "Store no more than X number of chains" quota has been reached.
In this example, deletion of oldest backup will occur immediately following creation of backup #5.
For your specifics:
You indicated your desire to retain 2 backups on a revolving basis. Thus, your setting would be "Store no more than 2 recent version chains"
Before deleting the oldest chain (oldest full in this example), the program would create the replacement first (full #3) and then delete the oldest full. The program will not perform a delete until the program has successfully created the replacement. As a result of this procedure, the user must provide enough temporary storage space for this short term need to occur, otherwise the program will error out as "full disk".
The key to how many backup chains to retain is the option
"Store no more than X recent version chains".
Should you indicate, your preference is for full plus some number of incremental's; or full plus some number of diff type backups, so indicate your preference and I will discuss those in a later post.
As I suggestion in my prior postings, the link #2 below provides answers to many of your questions as to "how".
Thanks for the info - got it now :)
I'm running Full Backups and choose to start the backups manually as needed and want to retain only the 2 most recent copies of the backup. I have it set for 2 now. Let's see how it goes.
Thanks again.
A mistake often made is to keep too few backups covering too short a time period.
If you have the storage space or can obtain more storage space, store more than you mght expect to use. In practice, it is often a backup is needed which is several months old. Also, one rule many of us 'ol timers practice is to never delete a workable backup until there is no other choice or solution.