What do I need to do to restore from an TIBX file that is accessed via a different path than when it was backed up?
Microsoft Surface Book 2. For various reasons (failure of the lower half of the laptop) we had to perform a backup of the system via Acronis Backup 12.5 over Wifi (no hardline ethernet on the unit, and USB ports were unavailable via the broken base unit) to another machine.
The Surface Book 2 has been replaced and is functioning and I'm now trying to restore.
The Acronis Linux environment struggles with the keyboard/mouse drivers of the Surface Book 2, so I built a WinPE 64 bootable media. However, Wifi is not available in the Acronis PE boot disk.
I do have an external HDD that I can now use on the new laptop since the USB ports are working. I copied the .tibx file from the computer where it was written to, onto the external hard disk, booted the Acronis WinPE loader and selected the file for restoring. It aborts, saying that it cannot get the URIs. Apparently, it remembers the path to where the file was originally stored (via the network), and is mad about it being on a local disk.
This makes no sense, since the TIBX is a self-contained single-file archive.
It appears that the URI mismatch in the metadata can be fixed in the older TIB format by deleting the XML file, but I can't find anywhere to fix up a TIBX URI metadata.
Who in their right mind makes a backup format that doesn't allow the backup file to be moved? This is WAY too fragile for the real world.
I was going to file a tech support query about it, but I see my maintenance contract has expired and I'm not sure I want to continue paying for this product if it's this fragile.
Any suggestions on how to fix this stupid TIBX fragility?