Preserve Last Full Backup from 4 Recent Versions
Hello,
Currently perform non-scheduled Custom scheme, Full backups with Store no more than 4 recent versions. I've just updated OS and want to keep my last OS backup just in case. I don't care about the 3 prior backups.
How can I preserve my last backup while still cyclically deleing older, previous backups?
Thanks for your time,
Alan
Yes that's what I ultimately did, just started a new task. Was hoping the "reserve" function would have been the key but evidently you need to know you need/want to reserve it before another backup is created.
I have the space, just need to monitor how many accumulate then delete them accordingly and hope I don't delete the last old OS backup.
Cheers,
-- Alan
Then your new backup scheme looks like this except that the "do not delete first version" is checked??
GH11. Create Custom Full Backup Scheme.Keep 4 versions (chains).
Yes, but "Do not delete first version" is not checked as the determination to keep 1 specific version was a recent decision.
Ok. If you new setting is "store no more than 1 recent version"
then after each new full, the single prior full will be deleted so only the newest full remains.
The program always creates the replacement first and then after creation, deletes the oldest full so for a few minutes during the backup process, there is storage space needs for two full backups.
My new task is storing 4 just like your example.
However, I've learned that whenever I create a new task, the new task ceases to manage old backups. Assume its due to ATI backup file auto naming reverting to the first backup name/number in its starting sequence. Doesn't seem to be any accounting for existing TLB files outside the scope of the starting sequence to age out/delete. I just delete them manually, after 4 deletions the new task and I are in sync.
A nice feature would be to keep any intermediate backup while creating and purging backups around the kept backup.
Cheers,
-- Alan
Any new task will only manage the backup files that is created by that specific task.
The purpose of the "automatic cleanup" option if for the program to do the cleanup and not the user.
If your task is full only and to keep 4, then automatic deletion will begin after full b5 has been created at which time b1 will be auto deleted by the program.
My recommendation is that when a new task is created, it points to a new storage folder so there is no intermixing of new and old backups. The old backups can remain untouched in their own folder. A new task always begins new with a new full backup. I practice that each new task also has a task name which differes from any other prior task.
If the backup scheme involves incremental backups,
once the task begins its creation of backups, the only backup that can be safely deleted by the user is the newest or most recently created, or all of the incrmentals. If the user deletes the oldest inc and newer inc remains, the newer will be useless as the task is now out of synce and the chain has been broken.