TIH 2012 - Reuse backup names with consolidation
Is it possible to create a scheme for 14 days where there's 1 full and 13 incrementals....then it restarts and reuses the filenames. Ie exactly So there will always be file 1 to 14
So I had a new backup created, 14 day cycle. Filenames of system only (ie no other parameters).
It seems to have created System.tib (28 gb) to System16.ttib.
Then System(1).tib is 28 GB again and off it goes with System(1).
But I would rather it overwrote System.tib. If I removed the First round of files at #16 would it then reuse system.tib or would it always just create a new set ie System(1).tib?
Post a screen capture of your backup scheme you are using so there is no guesswork (on our part) as to what combination of setting is in use.
Hopefully these show up.
David,
Item 1:
If I understand correctly that you want to create a backup chain for a 14day cycle,
you need a setting of Full +13 incrementals, so a new full would occur on every 15th backup.
(each chain length would be 14 backups files).
Item 2:
Understand that the option
"delete chains older than 15 days" is indicating that the first chain of 14 files must be completed , and backup #14 must be older than 15 days
So you would have 29 backups completed before the elapsed day count of 15 is reached (before backup #14 is older than 15 days.,.
The first scheduled deletion would occur after backup 29 (Full #3) is completed.
--------------------------
Item 2A: If item 2 was not your intent, you may have meant to choose
"delete chains older than 1 days" is indicating that the first chain of 14 files must be completed , and backup #14 must be older than 1 days
Deletion of the first chain of 14 files would not occur until after 2nd Full is completed.
-----------------------------------
Item 3: Consider using a backup scheme of
"Store no more than 1 recent version chain" . 1 being (n)
This would be equivalent to the item 2A but using a differnet method.
If you wanted to keep more than 1 chain of 14 files per chain, you could increase the "store numbe"r to whatever number of chains you wish to retain.
-----------------
Note, each new task should have a different name, so don't use "system" again. You could add a number or date to each new task if you wanted to use 'system" so each new name is slightly different but never used before.
For example:
name of task 1 could be System
name of task 2 could be System1
name of task 3 could be System2 or System-27Oct
In other works, Just keep each new task name to be unique so as to avoid confusion and correct identification.
---------------------------------------------------------------------------
If you have already started creating backups with your new task, I would stop using the old task,
but create a new task with the changed settings as making changes to an existing task does not work well.
This link may be of interest.
Ok I think we might be talking cross purposes.
Basically I want to create a 7 day or 14 day schedule - ie a new full either 7 days or 14. That will overwrite the filenames.
I want the file names overwritten as these will be uploaded to a cloud backup service...and so rather an an new individual filename for every single backup I want the entire scheme to use a consistent set of files.
Eg for 7 days I want
Backup.tib - this is the full
Backup1.tib
.
Backup6.tib
Then then next full starts
Backup.tib - full for week 2
Backup1.tib
.
Backup6.tib.
So when the cloud backup service runs, it will (in this example) have Backup.tib as 2 versions of the full backup and Backup1 to Backup7.
What currently seems to be happening is at each full, a new "version" number is being added - ie (1) (2) so every single file is always unique. This is what I want to avoid.
I only mention the 14 days, as I'm not sure how long it will take for the upload to take, so I may need a 2 week schedule, so Backup.tib then Backup1 - backup13
Be aware that version 2012 does not support Windows 8 or Windows 10.
Whether you choose a 7 day or 14 day cycle is up to you. The more frequent full backup is the safer choice, as when restoring an incremental backup, all prior backups of that specific chain
must be present and readable or non-corrupt
GH25. Understanding differences between Incremental and Differential backups for data recovery.
As per my examples, the option "store no more than(n} recent version chains is my preferred choice, as the (n) provides an easy method of setting how many chains you wish to retaink,
in other words, the "store (n) sets your quota of how many chains to retain.
As for the naming and overwrite, you will need to do some testing on your own. I am using 2016 and version 2012 was several years back, so I cannot give a definite answer about the name.
I do not believe it will overwrite and reuse the same name. If I remember correctly, there will be a number in parenthesis added to each file to indicate which chain is involved
If I remember correctly, the name identification will be something like
Chain 1 will be System.tib
Chain 2 will be System(1).tib
Chain 3 will be System(2).tib
Set up a test situation whereby you create a special backup task with your intended backup scheme;
but set the backup to non-scheduled and have the backup be a file backup with only 1 file being backed up.
You can then initiate the test backups manually and the backup will only take a minute or so for each backup.
YOu can then see what happens to the tib name and when the deletion occurs.
you can manually create many test backups in just a few minutes to see the results of your test.
Your own testing will provide the best answers as to whether the program will do what you want.
TrueImage Home 2012
https://kb.acronis.com/content/24061
https://www.acronis.com/en-us/support/documentation/ATIH2012/#17341.html
https://www.acronis.com/en-us/download/docs/atih2012/userguide/ATIH2012…