Skip to main content

Do not delete the first version of the backup?

Thread needs solution

I'm doing an incremental backup, with a new "full" every 30 days. I have been doing that for years, and since the manual consolidation feature disappeared I've been doing my cleanup by hand. That's a pain, because then you have to keep saying "skip" to get TI to understand what you've done.

Thinking I'd finally found a way around this, I told TI 2016 to store no more than 3 recent version chains, and I checked the "Do not delete the first version of the backup" box.

I thought this option would keep the "full" files while deleting the "inc" files. Apparently, I was dead wrong. All of my older full backups are now gone. I now have three full backups with their associated version chains.

So, what exactly does that box do?

0 Users found this helpful

Hi Jerry,
The option "Do not delete the first version of the backup", when checked, tells the program not to include that specific backup in any automatic cleanup (deletion) scheme. It will be numbered B1 and will be the first backup created when a new task begins creating.

There is no option to keep the full and delete all the incrementals, other than delete manually which causes grief to the progam and the user.

There is the option to set up a backup scheme with automatic cleanup which you set the quota on how many chains to keep ( chain length = the full plus how many inc's before the next full. Your chain length might be 30, if you are keeping 1 full pluls 29 inc)

If you set to keep "Store no more than 3 chains" (90 files), then automatic deletion of the oldest chain (oldes Full plus 29 files) will occur after 3 chains has been completed plus the next Full and and deletion will continue to revolve after each new Full in the future, so you would always have 3 months of backups. If you set the "do not delete the first vesion", it would be kept in addition to the other chains or keeping 3 chains plus the do not delete first full.

The GH12 below is an example.

------------------------------------------------

GH12. Create Custom Incremental Backup Scheme w/auto cleanup. ...Keep Full plus 6 Inc per chain. Store/Keep 4 chains. Use whatever number best fits your needs.

GH25. Understanding differences between Inc and Dif for Safety

Depending upon the type of backup scheme you wish to create, here is an example of each type. These can be set up for Disk image, or Partiton, or Files-folders backups. These example show how to set up automatic cleanup so the program will do the deletion after it reaches your set goal of how many chains to retain.

Editing an existing task is not recommended. Rarely does an edited task perform to user expectations. It is usually better to start with a new task using a new non-identical task name and point to a new storage sub-folder so each task has it own storage folder/sub-folder. Old task can be stopped or deleted from the task listings.

GH11. Create Custom Full Backup Scheme w/auto cleanup....Store/Keep 4 versions (chains). Use whatever number best fits the individual needs..

GH13. Create Custom Differential Backup Scheme w/auto cleanup. ...Keep Full plus 2 Diff per chain. Store/Keep 2 chains. Use whatever number best fits your needs.

GH64. 71342: 2015-2016 How to save a non-scheduled task.

GH63. 64640: Hints to help prevent issues with your TIB backup files creation.

GH63. 75086: A discussion on how to configure backup schemes.

----------------------------------------

Well, manual consolidation hasn't come back yet. I guess we'll have to wait to see if they put it back into ATI 2017.

There is a supported way of doing this, but you have to do it from the rescue media. That's not very handy.