Skip to main content

Restoring from .tib created in 2014

Thread solved

Hi there everyone,

I've just installed the latest version of TrueImage 2021 for Mac and tried to restore files from my old Windows backup created in 2014 with TrueImage 10 (or similar, I don't remember now).

When I tried to add those .tib files ("Add Existing backup"), TrueImage said "The metadata file corresponding to this backup is not found. Place the backup and its metadata in the same folder and try again."

Funnily enough - there're no files other than those .tibs, and they were the full backup I made in 2014...

 

Any ideas? :)

 

Cheers,

Samuel

0 Users found this helpful

Samuel,

TI 2021 uses a new file format (.tibx) and additionally uses metadata to track backup files.  These metadata files are created at time of backup creation.

It also sounds like you are dealing with a Full Disk backup file which would have a file format of (.tib).  The .tib format remains but is now used only in File/Folder backups.

You might attempt to recover files and/or folders from your backup using Windows File Explorer to navigate to this backup file location, then right click on the file, locate Acronis in the resulting menu, and see what options you have.  Hopefully one of those options will be Mount which would allow you to access files/folders in the backup file.

Samuel, another issue here is that the Mac version of ATI is not compatible with files created by the Windows version!

See the link in my signature for Backup archive compatibility - to read the files from ATI 2010 created in 2014 would require using ATI 2021 for Windows, or else booting from the Windows version of rescue media.

Steve Smith wrote:

Samuel, another issue here is that the Mac version of ATI is not compatible with files created by the Windows version!

See the link in my signature for Backup archive compatibility - to read the files from ATI 2010 created in 2014 would require using ATI 2021 for Windows, or else booting from the Windows version of rescue media.

I'd suspected it might be Mac-Windows issue... Thanks for clearing up the confusion Steve, appreciate the links to Acronis KB as well! :)