Corrupted backup in ATI 2016
I have a backup created on my old machine (Windows 8) created in ATI 2013 that I am trying to recover files from to my new machine (Windows 10 Pro) using ATI 2016. It is saying that the file is corrupt, so I'm trying to see if there is a real issue.I did a search and found this https://kb.acronis.com/content/1517 article, but when I tried to follow the link entitled Troubleshooting issues with corrupt backups, it opens the knowledge base page with log in required, but nowhere to create a log in.
Any ideas?
I'm going to guess that I'm out of luck, even though I thought that I recovered some files from here last night:
Benjamin,
There should be 2 more files associated with this backup:
C:\Weekly Backup_full_b1_s1_v1.tib
C:\Weekly Backup_full_b1_s1_v1-1.tib
Looks like the s1_v1-1 has disappeared, so that's the problem?
Benjamin,
At this point, I am not sure if there would be a s1_v1-1 file. The image below shows a file split that happened on one of my backups. The sequence is very strange, but shows no -1 file.
Have you tried to mount the s1.v1 file?
You could also try to validate the tibs?
Attempting a validation would create a log file, which could help us analyze your situation.
Benjamin,
Any chance you can try using the offline bootable recovery media and attempting to restore to a new/different location (temp folder so as not to overwrite anything ... just in case). Perhaps, it is a false positive in the 2016 application, but will still be able to restore using the default offline bootable media instead? As this appears to be a full backup, hopefully you can just point it to the first version of the backup file and all will work as expected unless it may truly be corrupt.
Usually, when you get the -1, -2 etensions, it's because the existing file name was already there and that one was corrupt or interrupted (network or usb connection dropped out, couldn't read from source, couldn't write to desintation, etc). Not sure if there's any real way to determine what happened in this case, but something prevented the original versioin of that poriton of the backup file from completing so it re-did it and appeneded the names to it since the possibly bad version of it was already in place at one point in time.
Please also see the ATIH 2016 User Guide page on naming conventions which explains the -2 suffix.
If you are creating a new backup, and there is already a file with the same name, the program does not delete the old file, but adds to the new file the "-number" suffix, for example, my_documents_inc_b2_s2_v1-2.tib.
I'll try and give that a go tonight, Bobbo.
FtrPilot: I tried to mount the v1 TIB from 2013, and once I'd got rid of UAC (which then caused Edge to stop working - if it isn't one thing, it's another...) I could access the files from Windows Explorer.
Benjamin,
If you can access in windows explorer, you should be able to copy them to a new or different location (per Bobbo's recommendation).
With regard to "rescue media", if the ATI 2016 rescue media doesn't work, you should try ATI 2013 rescue media.
Please keep us informed...thanks.
FtrPilot