Skip to main content

Instant Restore from .tib files created by True Image 2016?

Thread needs solution

Small business owner here, currently running True Image 2016 on Win10 machines. True Image used to have "recover to virtual machine" functionality, but that feature was removed. Acronis Backup 12 has that feature as Instant Restore.

Here's the setup I envision:
* Purchase one copy of Acronis Backup 12 for a desktop Win10 machine running Hyper-V
* Continue to run True Image 16 on all the Win10 laptops

And at last, here is my QUESTION:
Can I take a .tib file from True Image 2016 (produced on one of the Win10 laptops) and using Acronis Backup 12 (on the Win10 desktop) run the Instant Restore feature. Objective is to get a failed laptop up-and-running inside of Hyper-V on the Win10 desktop in 10 minutes.

I'd be happy to put Acronis Backup 12 on *all* machines, if it wasn't umpteen-times more expensive than True Image.  ;-)

Cheers,
Bruce.

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi Bruce,

The process you described _may_ work, but there are big chances that Acronis Backup 12 won't recognize .tib archives created by Acronis True Image 2016, since we've not tested such cross-product compatibility of the archives and therefore haven't fixed any possible bugs (since they were not revealed). In theory the structure of entire machine backups should be very similar between these 2 products, but the archive metadata will differ significantly and it's hard to say how it will affect the recovery. I'd guessed that entire machine recovery would work, but not "Instance restore" (aka Run VM from backup). Also note that "Instant restore" on Hyper-V will require "finalization" of the mounted machine on permanent storage, since it's only a temporary machine - see details in my reply to this thread (it's still a manual process since this "finalization" feature wasn't added for Hyper-V yet).

Thank you.