Skip to main content

True Image Home Backup locks Windows 7 (fails to backup)

Thread needs solution

When I try to back-up (Ext USB HD) my system locks up and no back-up is created.

The initial True image window appears telling me "Creating partition image 1 of 2)" then, whilst I am at least able to move that window, the whole OS eventually (within about 2-3 mins) effectively freezes and no mouse control is possible. The screen then goes black ( I have left it to se if it self recovers) such that I have to reset the PC. Are there any True Image log files generated that may help with this issue?

On some ocassions a zero byte .tib file was created but mostly nothing results. Can anyone help? My system is Windows 7 Home Premium.

Thanks

Tony

0 Users found this helpful

You need to tell folks here whether you are using the bootcd or starting the backup within windows. And where you are backing up from and to and what kind of backup you are attempting. ATI does create a log, which can be viewed under Tools in the older version (through 11) -- not ssre but its somehwere under the menu in newer versions.

If you can't get ATI to run long enough to show yo the log, you can view the log file natively; the log file is stored in
C:\Documents and Settings\All Users\Application Data\Acronis\TrueImage\Logs

or in

C:\Documents and Settings\All Users\Application Data\Acronis\TrueImagehome\Logs
and it is an xml file, so you'll have to plow through all the xml code stuff but it's still visible with a simple text program like notepad.exe

Somebody correct me if the 2009 or 2010 versions use a diff location.

This might not help, but just to take a crack at it, this prob sounds like something that can happen when using the bootcd -- in which case using the usbmouse=off parameter might help if you are using a usb mouse.

The zero byte file just means that the program created the file handle and metadata entry in the file system but was unable to write any data to the file, perhaps because it was unable to read from the source disk or because some other prog prob hung the PC before it could write any data to the file.

Scott,
Thanks for the tips and advice. I am running ATI (Home build 6,053) from within Win 7 and simply trying to backup my whole C Drive to an ext USB HD - I am using the simple command "Back Up My System" which is in shown on the "Home" tab in this new version. My entire C drive is currently at 112Gb and I have plenty of spare space on my ext USB HD.

My PC is running C Drive on a twin 300Gb disk array set up as RAID 1. Neither Windows nor the "Intel(R) Matrix Storage Manager" complain of any issues with the array so I do not believe this is the cause - unless this version of ATI Home cannot handle Raid arrays.

ATI can see the HD OK and offers no complainst - indeed if you check the attached log file you can see it just seems to stop at "message="Locking partition C:..." module="1" time=" ...

Interestingly when I tried to save the log file (from within ATI - note the Home 2010 HMI is differnt to that which you describe) the log file was created as you can see attached but ATI complains "Failed to save log file "C:\Users\Tony\Documents\Temp\logs.log" - strange because the file is actually created - could this whole problem be an issue with ATI home not being allowed sufficient write privilages? Not ethat the last line of each failed backup in the logs is "Locking Partition..."

The log file mystery is probably just a case of Win closing the file off as good housekeeping after it's been created, even though ATI at some point becomes unable to address it and therefore reports an error in the save log file operation.

The other matter is deeper down in ATI and I think ATI Tech will have to step up. If Win can see the RAID, then ATI should be able to see it for backup. So I suspect a driver conflict between ATI and something else.

You might try using msconfig to remove all the services ans startup progs exdcept for ATI stuff and MS services and see if the prog works then. If so, then one of the other services/startup progs is in conflict and it's a process of elimination to find out which one ATI isn't getting along with.

Just curious (its not a fix, but for the time being might help make backups) have you tried to do a backup from the bootcd? That's something you also have to test since it's linux OS and whether it works is indepepndent of whether the Win version works. Although, probs with the bootcd working are usually driver issues that can be fixed by getting an ISO with the right drivers to burn to CD to make a boot disk.