Acronis True Image 2020 .tib to .vhd
Hello,
Everything is in the title.. How can i change a .tib file to a .vhd file in Acronis True Image 2020 ?
Thank you for your help.


- Log in to post comments

Does the fact that there is a TI- number assigned imply that it's an issue they are planning to fix?
- Log in to post comments

The TI number is an internal reference used by development for issues they are investigating but I do not believe this guarantees that a fix will come at anytime soon!
- Log in to post comments

Sorry to resurrect the thread, but this kind of amazes me. These are basic features of a modern backup utility. For all that they've given up what if any benefit is there to .tibx over .tib?
- Log in to post comments

See the following KB documents published by Acronis with regards to .tibx files.
KB 63518: Acronis True Image 2020: do not delete first tibx file
KB 63227: Acronis True Image: Do not delete .TIB or .TIBX files outside of Acronis True Image
KB 63498: Acronis True Image 2020: new tibx backup format FAQ
KB 63425: Acronis True Image 2020: Limitations of tibx backups
KB 63445: Acronis True Image 2020: how to view and manage backup versions in new backup format
KB 63444: Acronis True Image 2020: tibx backups in local destinations
KB 63613: Acronis True Image: local backups are not available for recovery if "metadata" file appears in the backup destination - if you see metadata file(s).
- Log in to post comments

That's a setback.
Regarding .tibx files, at least I was warned about limitations, but why can't I restore .tib backup to vhd??
There's a backup that what started in True Image 2019 and continued in True Image 2020. Trying to restore it to vhd (in either True Image 2020 or True Image 2019), I get
"Recovery to the original location failed due to an error.
A format/resize error."
When trying to use option 'Convert to vhd', I get 'Unable to convert backup to Windows format'.
At the same time the .tib older backup that was untouched by True Image 2020 restores successfully.
- Log in to post comments

J.V. welcome to these public User Forums.
Sorry but I am not sure exactly what you are asking here?
ATI only offers an option to Convert a (Disk / Partition) .tib to VHD, as documented in the ATI 2020 User Guide.
There is no option offered to recover or restore to a VHD, so am puzzled by your using these terms in this context?
If I select a Disk .tib backup of my Win 10 SSD created by ATI 2020, then the Convert to VHD will create a new .VHDX file which I am then able to open by double-clicking in Explorer.
See forum topic: How to create a Disk backup as .tib (not .tibx) which will create a new backup task using the older .tib format in the Windows ATI 2020 GUI.
- Log in to post comments

Hi Steve! Thank you for quick response.
Sorry, looks like I mislead you a trifle. I just have spent another 5 hours over the problem and was going to edit my post, based on new information.
As for VHD convertion, there are 2 methods I'm aware of:
1) to use 'Convert to VHD' method as you described above;
2) to manually create VHD via Windows disk management, mount it as a partition (Acronis is not involved in this part) then run Acronis and restore backup image to this mounted partition as restoration target.
I believe that the result is the same in each case.
I was successfully using both methods previously to obtain bootable VHD with earlier version of my system (so to be able to check out how some things were working previously).
Now with 2020 I tried to do the same thing, but got errors in both cases. Based on information about the lack of VHD support in .tibx, I initially suggested that the error was connected with me using VHD.
But today I tried to restore my backup to physical drive (had to create new partition on my external HDD specifically for this purpose) and got the same error.
All this leads me to conclude that the problem lies in backup image itself (there are 2 version chains, i.e. 2 full backups, but I cannot restore any of them).
The catch is that Acronis successfully validates image. So for 3 months I believed that I had functional backup, though in fact I didn't. Seems like I cannot rely on Acronis anymore.
And another thing I haven't mentioned: any attempt to restore the image DESTROYS target partition.
On my external HDD I ended up with unallocated space in its place after unsuccessful restoration attempt, the same was with VHD.
- Log in to post comments

Whenever you are doing a Disk level restore of a backup image, the first action will be to wipe the target drive in order to then assert the partition layout from the restored image file. If the restore operation fails after the wipe, then this will give the result you are seeing as being a destroyed partition!
The earlier error you reported for a 'format/resize error' is most commonly caused because the target drive (actual or virtual) is smaller than the size needed to recover the backup to, including doing any automatic resizing of partitions.
One further comment, with .tibx files, it is very important not to delete any files from the version chain other than by using ATI to do so by using either automatic cleanup rules or else the 'Clean up versions' feature for the backup task. This is because there are dependencies with .tibx files that did not exist for previous versions of ATI using .tib files.
- Log in to post comments

My backup is in .tib format since it was continued from 2019 version.
As for the free space, this was my guess also, but...
In the first place, shouldn't Acronis warn me if target partition is too small? Actually it usually does, that's why I considered that if I can press "restore" button, then everything is OK.
Apart from this, 'Convert to VHD' option isn't limited in regard of free space (it takes as much as needed to rite VHD) yet it gives error anyway
The original partition (which backup was made from) is 101 Gb in size with something like 80Gb occupied.
I tried restoration to 120Gb VHD (failed), 90 Gb physical partition (failed) and 90Gb VHDX (dynamic size), failed as well. I believe dynamic size allows to stretch partition size as needed.
BTW, I can mount image, no problem with it. So I don't think it's really corrupted or something.
P.S. Just to be sure, just tried to restore to 200Gb partition. Failed
- Log in to post comments

Why don't I have this on the menu? Acronis True Image 2020, 22510
- Log in to post comments

Sergey, see KB 63425: Acronis True Image: Limitations of tibx backups - which may answer your question.
- Log in to post comments

Steve Smith wrote:Philippe, welcome to these public User Forums.
See the ATI 2020 User Guide: Converting Acronis backup and Backup operations menu but note that this option only applies to .tib file format, not to .tibx files!
Hi,
choosing an incremental filesystem backup usnig tib files there is no menue to convert to vhd.
- Log in to post comments

frodo wrote:Steve Smith wrote:Philippe, welcome to these public User Forums.
See the ATI 2020 User Guide: Converting Acronis backup and Backup operations menu but note that this option only applies to .tib file format, not to .tibx files!
Hi,
choosing an incremental filesystem backup usnig tib files there is no menue to convert to vhd.
Hello!
Please review the following limitations:
-
A file backup cannot be converted to a .vhd(x) file.
-
To boot from a converted .vhd(x) file, it must contain:
- A system partition of the same computer. You cannot boot other computers using the same .vhd(x) file.
- Windows 7 or later operating system.
-
Any changes you make to a booted or mounted .vhd(x) file are saved to it. If you boot from a .vhd(x) file and make changes to the data that was not backed up, these changes will affect your live system.
-
The standalone versions of Acronis True Image 2020 that start when booting from the bootable media do not support conversion operations.
-
Acronis True Image 2020 cannot convert .tib files that contain dynamic volumes which were originally located on more than one disk drive (for example, spanned or striped dynamic volumes).
Please ensure that your situation is compliant. If it is, please provide more details regarding the type of backup and disks involved.
Thanks in advance!
- Log in to post comments