#ACRONIS TRUE IMAGE HOME 2009 KEY FULL#
#ACRONIS TRUE IMAGE HOME 2009 KEY WINDOWS#

So I have solved the problem by uninstalling TI 2009 and reinstalling TI 11. And the chances of getting a network timeout or 'Delayed Write Failure' during the process are very high.

#ACRONIS TRUE IMAGE HOME 2009 KEY FULL#

But the consolidation done by TI 2009 seems to thrash the destination disk so heavily that it takes FAR longer than a full backup.

This has proved very reliable for ordinary backups using either Ghost 9 or 10, and TI 11. In my case, I do backups to a network share hosted by an XP Home system where the physical disks are external in Firewire-800 enclosures. With the TI 2009 scheme of avoiding destination overflow through consolidation, the time of your longest backup seems to be highly variable, and definitely longer than the time of a full backup. When your destination starts to run out of space, you can delete (or move elsewhere) the oldest full and its sequence of incrementals. With traditional (TI 11) style incrementals on a fixed schedule, and a full every n incrementals, the time of your longest backup is the time it takes to do a full backup. Most users do WAY more backups than they do recoveries or mounts of images - if you're lucky, you may never do either one except for your initial testing to verify that it's possible.

You'd still have daily granularity for as long as you want it and have space for it.Дoes that make sense? Anybody know if the consolidation stuff is really that good? Certainly the TI 11 handling of quota violations (or the way that Norton Ghost 10 tried to deal with running out of space) was not something you'd want to have happen very often.Д®ven if the combination of naming and scheduling can be worked out to produce backups that have the property of daily incrementals from a weekly base, that can go on 'forever' without filling the destination by virtue of consolidation, there's still an issue.

#ACRONIS TRUE IMAGE HOME 2009 KEY WINDOWS#

If the consolidation stuff really works well, then maybe you could get an effect similar to, say, daily incrementals with monthly full, by setting the consolidation threshold at 30, and then running a separate Windows scheduled task to run every 30 days and copy the full and its 30 incrementals to a different area. I guess that would be kind of consistent with what appears to be the default of just 2 backups if you enable consolidation based on number of backups: in that case, each backup of live data gets done in the time it takes to do an incremental, and then there's a bunch of post-processing of just the backup data. Maybe the idea is that the new consolidation stuff is really great - both that it's fast, and that consolidating a full with n incrementals results in a full with 1 incremental that is identical to what you would have gotten if you made a full instead of the (n -1)th incremental, and then made one incremental off of that. Click to expand.That sure does sound absurd.

Acronis true image home 2009 key