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?
Seriously, like, if Microsoft Word refused to open a .doc file because you'd moved it from Documents\Client\Active to Documents\Client\Inactive, people would be calling for blood.
Hello Chris,
welcome to Acronis forums!
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.
Chris, please make sure that you copied the entire backup archive.
The URI mismatch error indicates that the backup archive is inconsistent (e.g. some of the incremental slices were missed).
We recommend using Export Backup in order to copy a backup archive to another location without any loss.
Well, I'm not sure how I could have failed to copy "the entire backup archive". There is only one file that appears to be part of the archive, it's named
DESKTOP-R81GF7M-DAD7F712-80E6-4EA6-8C7B-C11DCA0DDC65-7E6BB6B1-4A8D-4678-BF02-279876F89EB4A.tibx
I copied that file.
Your answer is very uninformative. I mentioned I had copied the tibx file, but your reply didn't tell me, for example, what OTHER files I might have missed.
I will try doing the Export operation, but I still think having to manually perform an operation on an archive file in order to make it portable is introducing unwanted fragility in the system. If I'm hitting my backups, things have already gone wrong, and don't throw more unnecessary obstacles in my path to restoring things.
I've tried doing Export twice now over the SMB share and it keeps aborting because of wifi issues.
Explain to me again why this is better than just letting me copy the tibx file to an external drive and restoring from that? Why doesn't it work and what needs to be done to make it work?
Hello Chris.
I've tried doing Export twice now over the SMB share and it keeps aborting because of wifi issues.
Wifi problems could cause backup inconsistency while transferring their data.
If a .tibx backup file could be browsed from the original location but could not be from another one it means that this file became inconsistent. You may check it by comparing the MD5 checksum of these files in both locations.
Another possible cause could be an attempt to read this .tibx backup from this specific external drive. In order to test this variant, you can create a new fresh backup to this external drive with Acronis WinPE media and see if this archive is available for explore/recovery. Otherwise, please try copying your original .tibx file to another external drive.
Explain to me again why this is better than just letting me copy the tibx file to an external drive and restoring from that?
Export operation not just copies the .tibx file but opes it, reads the backed up data and copies the data to a new archive on another location. Thus, it ensures that the data could be properly restored from this backup (it is not corrupted).