How to do consilidation right?
Hi,
I am using bulid 6131 of True Image Home 2012 and it has been working ok so far.
Then I wanted to do a consolidation but like with older versions everything got completely messed up again. The hard drive of the backup is full and I actually just would like to keep all the updating jobs as they are and get rid of say every second backup. How can I do that without switching to another drive? I have one which could be temporarily used.
Trying to switch the drive and job led to freaky file names like 'consolidated version22(1)24' and even led to one incremental file being put back on the drive of the original backup.
I have deleted all files of the consolidated version now and am back to the original backup files.
I just want everything as it is just with less backup files. How do I do this?
Thanks!
Consolidation doesn't work with TI2012, at least not on my machine. In my case the consolidation will hang, but even when it works it will regularly lose track of one or more incremental files and will have to be started again from scratch.
Don't worry. Its not as if the product is working with valuable data or anything ... oh, hang on.
ati2012 has a bug where you have to set the number of incs to greater than 1. :(
Here are some sample backup schemes which have proven works and these involve keep x number of backups rather than get involved with disk space or elapsed time. Change the x number to fit your needs.
Custom Scheme; Backup method= Full; Store no more than x recent versions.
http://forum.acronis.com/sites/default/files/mvp/user285/2012-5545/2012…
Custom Scheme; Backup method= Incremental; Store no more than x recent version chains
http://forum.acronis.com/sites/default/files/mvp/user285/2012-5545/2012…
Custom Scheme; Backup method= Differential; Store no more than x recent version chains
http://forum.acronis.com/sites/default/files/mvp/user285/2012-5545/2012…
Thanks for your replies.
@GroverH:
Considering your second scheme: What does 'version chain' mean? It sounds like it means full backup plus incrementals but written in blue it says 'recent full backups'. Do I need full versions? I think this make the backup significantly bigger...?
@Scott Hieber:
How do I delete a task? I didn't find it in the 2012 version. It looks like the task is bundled to the backup files!
If I could find this I'd probably try a combination of what GroverH suggested and move to the other drive (I know that's different from what I originally wanted to do...).
You can right click on the settings button on a task and get a list of possible actions, inlcuding delete. It's in the User Guide. If yu want to keep your existing backups, then move them to another location.
E.g., see page 20 in the User Guide
But this will delete data files as well, right? I want to consolidate my backup to a new place and create a new task to add incrementally to the new location just as it is doing now. Since I am not sure if it works I want to keep the non-consolidated backup files until I see it works properly with the files in the new location. However, I only want a task to add to the consolidated version and not to the non-consolidated version.
Yes, unfortunately that is the way ati is set up to operate. So move them to another location before you delete the task.
When you reload ati, it will probably find the old tibs if they are on a disk connected to the PC so don't delete those (they might show up as a task without settings or as a seperate task for each tib) so you have to be careful what you delete on the list of tasks. This is one of the more unfortunate aspects of the newer vesion of ati that uses an internal database-- it has trouble distinguishing between backup files and the tasks that make them--it wants to lump them together into something Acronis calls a data set (sometimes it will make a bunch of little lumps, puting several tibs in diff tasks/data sets that were all made with the same task. this is supposed to be easier for novices, but. . .
Thank you! I think I really became a victim of this. As I said in my first post: The task for the consolidated version created an increment to the location of the old non-consolidated version.
Sometimes it's best to jsut delete everything and start over. And one you have a task setup, don't edit it or change in it any way. If you need to make a change, it might take or it might start treating subsequent backups as a different task -- if you're doing incs this can cause all kinds of confusion. so changes are best made by delete existing task and creating a new one. This has generally been true for the 20xx series of ati.
Okay, so just to double-check here is what I'll do:
1) Consolidate to new location
2) Move old backup to another folder so Acronis can't find it
3) Delete old job in Acronis (files won't be deleted cause Acronis can't find them)
4) Create a new job with the consolidated version and make sure I make it correct cause I mustn't do any changes to it
Considering the new job I'm still wondering about GroverH's reply:
http://forum.acronis.com/sites/default/files/mvp/user285/2012-5545/2012…
a) What does 'version chain' mean? It sounds like it means full backup plus incrementals but written in blue it says 'recent full backups'.
b) Do I need full versions? I think this make the backup significantly bigger...?
I'd make a new file from scrah, not based on an exting backup. just tell it you eanty incs. it will make a full the first time.
JA,
Considering your second scheme: What does 'version chain' mean? It sounds like it means full backup plus incrementals but written in blue it says 'recent full backups'
A version chain is the definition for a backup which consists all the parts of the single chain.
A new version chain is created every time a full backup is created. If only fulls are created, then each full is an individual version chain. If 10 full created, you would have 10 version chains.
If you want incremental or differentials subsets, after the first full, each inc or diff is part of that specific version chain. When the next full is begun, a new version chain is begun with inc or diff subsets. If you had a custom backup scheme to keep 1 full +6 incrementals , after 3 fulls, you would have 3 version chains with each version chain consisting of 1 full + 6 inc or 21 backup files.
This is an example of differential retention.
http://forum.acronis.com/sites/default/files/mvp/user285/folders/win7-6…
