TI 2009 Build 9646

If its doesn't validate all the time I'd find out why and fix the problem.

By the above system the only ones I'd keep are the 5 star ones. However, if the archive validates properly at least once then there is not a problem with the archive file but with the "reading mechanism", most likely a marginal hardware issue or a marginal driver for the hardware issue.

 

Got it installed, and created a new Rescue CD. The major deficiency for me that started with version 11 still has not been fixed!

That is, after the first selection screen, my Wacom wireless mouse does not work, and I have to stop and plug in a tempoorary USB mouse. The Wacom mouse worked fine through all versions up to and including 10.

I would suggest that Acronis go back and use the version of mouse.com that was with version 10.

It's not a deal breaker - but it is a PITA!

 

Did you create a new Rescue Media CD with Build 9646? Perhaps after installing Build 9646 you first have to set the default option to not exclude any files before burning a new Rescue Media CD. Booting from this CD hopefully the box should not be checked to exclude certain file types.

Did somebody try this already?



This is what Acronis promised some time ago:

"Re: Office 2007 corrupted after image restore using TI 2009

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

Hello everyone,

Thank you for choosing Acronis Disk Backup Software.

Thank you for reporting this. The issue was forwarded to our Development Team with high priority some time ago, and is expected to be fixed in the next released build. We apologise for the inconvenience caused.

For now, as had already been discovered in this thread, the solution is to remove "*.bak" files from the list of exclusions (or turn off exclusions completely).

Thank you. "

 

Yes hajohobbes I checked it out. The box to exclude certain files is unchecked as a default when creating an image in Windows. Creating a rescue media CD does not import those defaults from Windows. This is a function of the Recovery Manager which we cannot change.

It doesn’t matter if the Rescue Media CD is created directly in Windows or by creating an ISO and burning to a CD, the end result is the same. The box to exclude is checked.

Bruce

 

@Bruce

Although the box to exclude is checked - can it be unchecked or is there another way to create an image booting from cd with no exclusions?

Thanks

 

Yes, it can be unchecked. The issue here is that many users won't know that it exists or where to find the option to uncheck it. I know many people that want to do backups but never take the time or have an interest in the details. It's tough enough just to get them to register the product.

 

Re: ALT + Help -> about screen

Exactly where is "ALT + Help -> about screen"?

Thank you

 

Open TrueImage Home 2009. Press the Alt key on the keyboard. In the upper left corner you will now see two entries, File and Help. Click on Help and pull down to About and click on it.

 

Re: ALT + Help -> about screen

Start TI.
Press the ALT key and you will notice a bar appear near the top of the Acronis screen. It will have File and Help listed.
Click on Help then About as typically done.

 

Re: ALT + Help -> about screen


-------------------------------------------------------------
Image highly compressed to reduce load time.

 

Thank you... some things are just too simple that you miss it.

 

Happy to hear that it worked out.

 

I did not see this. I installed 2009 and tried (1) creating a new scheduled task for a full image backup, and (2) starting a full image backup without creating a task. In both cases the "Exclude..." box was checked when I got to that page in the wizard.

 

I think what it means is that auto consolidation is not available for full backups, and this has now been made clear. The manual says (pg.33):

If you select the Full method, the Automatic consolidation step (see 5.3.7 Setting automatic consolidation) will be disabled. If you are adding a backup to the existing backup archive, the Full method will be unselectable.

This is the $64 question (or one of them). I see where you can now tell it to start over with a full after a certain number of incrementals. However I don't see (1) how you can tell it to keep a previous archive when doing fulls, or (2) how to keep the previous set of full + incrementals when doing incrementals with a limit.

Anyone else see something I've missed? Could renaming via a post-backup command work here? Anyone?

 

I just ran a full backup from within windows using the settings you see in my screeny. It didn't mess with any of my other backup archives. Is that what you are talking about?

 

It's the "overwrites existing backup archive" that's the problem. We want to be able to keep previous full archives.

 

Well I'm confused then. I have done several image creations on two different systems with TI 2009, and it hasn't touched any of my previous full archives.

 

How has it named the archives?

 

I create my own names for the archives. So, each name is different. Usually I use the date as the name.

 

Okay, so I created a task to "create new backup archive" of a partition to location "test.tib" on another partition. I ran it once and ended up with test.tib. I ran it again ten minutes later and ended up again with test.tib, ten minutes younger. My previous test.tib is gone, overwritten.

 

I ran the same test. I did a full backup of my OS drive, and let TI name it. TI named the image file "MyBackup.tib". I then created another image, and once again let TI automatically name the file. It named the 2nd image file "MyBackup(1).tib". It kept the previous image file (MyBackup.tib) completely in tact.

 

I see. Then there is no problem. What I (and others) want to do, and which we were able to do prior to 2009, is run a scheduled task on a regular basis to take a full image backup and not overwrite the previous full image taken by the same task, without manual intervention. In my case I accomplished this by running a post-backup command script that renamed the archive just created, but this is no longer possible.

 

Can you tell ATI to leave only x many Full backups and then delete the oldest? I.e., a task runs automatically that creates Full backups only and doesn't overwrite previous full sbackups but when the number of Fulls goes beyond a user-set limit, it then automatically deletes the oldest Full?


sh

 

Ok, I see. So basically this over writing the previous archive only happens if you schedule image creations? So when a scheduled image creation starts, does it automatically name the new .tib file the same as the previous image file created? And that is why the old file gets overwritten?

 

Yes, for a full backup. An incremental or differential backup names the new backup ...2.tib, ...3.tib, etc.