True Image 2009 Creating multiple files and eating HDD!

Hello

TrueImage 2009 is set to do an incremental backup every weekday at 5pm. It said today there is not enough space on the drive. So I looked and found this:

http://img26.imageshack.us/img26/2254/backups.gif

Can anyone tell me:
what is going on
what the bug is
if I have a safe backup
what to do to get this working again
what to do so this does not happen in the future

Many Thanks!

 

I don't know if it is just my computer but the image is too small to read what is in it.

 

Try this: http://img26.imageshack.us/img26/2254/backups.gif

 

All those tib files with number ID strings after the name are temporary images.

These normally appear when 2009 tries to consolidate an archive. If there is not enough disk space then these aren't deleted as they would be once the final file has been amalgamated.

You also get this numbering if using the SZ or in other versions of TI using auto location places or vaults.

 

I have a feeling its set to consolidate archives. TrueImage slows the computer down enough when it runs, if I remove that option, can I continue making backups successfully?

 

Yes you can, but be warned deleting those temporary files may confuse TI when it comes to make the next image.

The best thing to do, will be to keep the original full image, delete all the others and then start again.

Your options are to get TI to consolidate at a much lower archive size, so the process won't run out od disk space or make your task so that at some stage it overwrites the previous files.

 

Ok, I think I will create a new backup. But really I think its a problem with True Image.

The actual backups come to 16GB. The temporary files are 50GB. So theres something not right there as it should not take more than an extra 16GB to consolidate a 16GB archive!

 

you are right, it does seem to have got confused somehow. It looks as though it has made working files of the working files. I wonder if your system went in to sleep or standby mode or something like a background defragger started working.