TrueImage 2020 is creating corrupted backup files
I recently restored my computer from a backup done in 2019. All went well.
I updated Windows10 (20H2) and all drivers and went to create a new backup. Each time I do the new backup I select the validate option and each time the file appears to be created just fine.
To test the file I reboot and attempt to restore from the new file. Each time I'm advised that the file is corrupt.
I've made four separate backup files, they're all saying the same thing.
I ran a CHKDSK on each partition in the drive, it all comes up good. This is an internally mounted Western Digital 5TB disk.
I downloaded the Western Digital Lifeguard software and it too says the drive is good.
I backed up my files to an external drive and then deleted each volume on the drive and recreated the partitions. Everything still checks out good.
Every backup created since the last week of the year comes up with a corrupted file message.
I'm running build 3 of the TI2020 program with a WinPE based bootable media (from USB flash drive).
Of course, my 'support' expired on December 31st so I'm out of luck there. I've spent the last five days trying to get this to work and I'm becoming very frustrated.
Any suggestions on what might be happening?


- Se connecter pour poster des commentaires

Rich,
I would suggest that you perform a new backup using the WinPE media of your 5TB disk. When you configure the backup make sure to select the Option - Method as Full as the default is Incremental.
Then after the backup completes once again navigate to the location where you created the backup file, right click on the file and select Validate. Does the validation succeed? If yes it should work for recovery purposes.
Since you mention use of a 2019 backup you used to make the initial recovery, was that backup made using the TI 2020 product or a TI 2019 version? If you used the TI 2019 version to create the backup, did you import that backup task into TI 2020 and are using that to create these failing backups?
- Se connecter pour poster des commentaires

So, I did another backup using the new media and made sure the file name ended in *.tibx.
That one worked fine.
I renamed the 'corrupted' files from *.tib to *.tibx and those validated fine.
I never knew about the tib vs tibx file format issue. You'd think that would be a little more clear. For example, if you're doing a full backup it would automatically name as a *.tibx file and not give you a prompt for either/or when naming the file.
At any rate, it seems to be working fine now.
Thank you.
R
- Se connecter pour poster des commentaires

Good to hear. Just remember that Disk/Partition backups will use a .tibx file whereas File/Folder backups will use the .tib file format beginning with the 2020 product.
- Se connecter pour poster des commentaires

Yeah, I'd been using the .tib format for years and there was no indicator that a change had been made when I started using TI2020. It would be nice if TI would recognize what type of backup was being done and automatically apply the correct file format. As it is, when you type in your filename you also have to enter the extension and that's where my mistake was made.
- Se connecter pour poster des commentaires

Rich, whenever I have created disk backups using the ATI 2020 (or 2021) rescue media, it has always defaulted to creating a .tibx type backup image file. The only time when this wasn't offered correctly, if I remember correctly, was during the initial Beta testing program for 2020 when this was all new to everyone and we were still expecting to be using .tib files!
The above image was captured back in May 2020 when doing a backup using rescue media at that time.
- Se connecter pour poster des commentaires

Yes, I think that's true. Until you want to name the file and then see your options are tibx or tib and you're used to tib files for the last 6 years, lol...
Now I know.
- Se connecter pour poster des commentaires