Attempted Copying an Incremental Backup, now Incrementals are all "Corrupted"
Last night I was trying to make a copy of the latest (out of three) incremental backups (the original full version is still intact, however it is over a year old), but Windows Explorer decided to hard crash to the point I had to reboot mid-copying. I log back in and now I cannot access my incremental backup files at all and keep receiving a corrupted message. I've also tested it on another machine, same error. Is there anyway to fix this?
Yes I was definitely copying it. I was trying to make a copy of the same backup in the same folder.
With ATI 2020 and later versions using .tibx files, there are many more dependencies between the files such that if you want to copy these files you need to copy them all and not leave out any files, plus not attempt to use those files while the original files and backup task is still present in the list of backups in the main GUI.
The copied files should definitely not be stored in the same folder as the originals but should be ideally on a different drive or partition.
If you wanted to use the copied files with ATI 2020, then the original task and files should be removed first by using the Delete option, so that the internal database is purged of all references to where those files were stored originally, then you can use the option to 'Add existing backup' in the GUI and select the most recent .tibx file in the copied files location to add it back again from that new location. Only one file needs to be added in this way.
Ok, but when I attempted this on my other machine, it still says its corrupt. Is there no fix for the corruption?
Just realized I had swapped the settings a long time ago, they're actually full backups each, so I cannot access them at all.
Did you make any changes to the original backup files either when or after copying them?
Have you tried to validate the original files?
Unfortunately with the new .tibx architecture there are dependencies even between full backups.
Changes in what way? And yes, I have tried validating the files but received the same error. It's only the original backup I am able to access.
Are you saying that the original backup files are OK and can be validated etc?
If yes, then that is what I would expect here if you have been trying to get ATI to use the copied files or to validate them etc.
Sorry for the confusion. So I have the original file dated December 4th, 2020 (this validated 100% and I can access it), and three full versions after that dated: November 26th, 2021, December 3rd, 2021, and December 10th, 2021. Those three I cannot access at all. What I was attempting was making a copy of the December 10th one, and file explorer crashed mid copy, so this corrupted them.
What is the size of the original / first .tibx file? It should be only 12 KB and contains vital metadata that is required to access all subsequent .tibx files in the sequence, so should never be deleted, renamed etc.
See the following KB documents published by Acronis with regards to .tibx files.
KB 63518: Acronis True Image 2020: do not delete first tibx file
KB 63227: Acronis True Image: Do not delete .TIB or .TIBX files outside of Acronis True Image
KB 63498: Acronis True Image 2020-2021: new tibx backup format FAQ
KB 63425: Acronis True Image: Limitations of tibx backups
KB 63445: Acronis True Image 2020: how to view and manage backup versions in new backup format
KB 63444: Acronis True Image 2020 and 2021: tibx backups in local destinations
Sorry forgot to include that.
Edit: Oh, I just found the issue, I was not aware that renaming the first file would "corrupt" the rest. After I removed the "(December 4th 2020)" it works. Now the question is, how can I make a copy of that December 10th backup that does not require the original file?
The core issue here is that there is no 12KB metadata file present which is required for these further files'
KB 63518: Acronis True Image 2020: do not delete first tibx file
So how do I find this metadata file?
Sorry but unless you have a copy of the file from before it was deleted or can undelete it then there is no method of recovering it or the associated files to my knowledge.
Vex Vex,
You can try using Windows File Explorer to find your 12KB metadata file, it may exist still in a temp file somewhere in your users folder or the Recycle bin. In the Explorer search enter .tibx and hit Enter. You can change the View options of the output window to show details so that you can easily tell if any 12KB files still exist. If you hover any file and right click you can select properties to see the path location of any file
I think there is some sort of confusion. The backups work again and I can access them and they validated 100%. The issue was me renaming the original backup (.tibx) to a different name. Acronis never created a metadata file in that folder. My remaining question is how can I make a copy of the last backup so it does not get deleted in three weeks.
The file that you changed the name of was originally "SAMSUNG SSD 970 EVO PLUS 1TB.tibx". Because your cleanup rules state that you want to always keep the first copy, it is not reduced to 12KB as would normally be the case. So don't worry about that. I think it is OK, and since you say it works after changing the name back you're good.
I am a bit confused that the file has a 12/4 date on it. I can tell you that file dates get confusing because when you create a backup, prior backups in the chain can get modified. 12/4 is not on your weekly backup schedule so not sure what happened on that day.
I don't know if this will work, but might be worth a try...
Copy the 12/10 version to another folder and give it a completely separate name, e.g. "Samsung 12-10 Copy.tibx". Then see what happens if you use Acronis to "Add existing backup" for that copy. It might load it up as something completely disassociated with the regular backup chain.
That 12/4 file, was when I started this new custom scheme for my backups to back up every Friday at 6AM. The settings are set to keep the original one (12/4/2020), then to store no more than 3 recent versions after that one. I will try copying that 12/10 file though like you suggested.
I tried the copying method, did not work at all. I guess unfortunately it relies on the original one for me to access it.BrunoC wrote:The file that you changed the name of was originally "SAMSUNG SSD 970 EVO PLUS 1TB.tibx". Because your cleanup rules state that you want to always keep the first copy, it is not reduced to 12KB as would normally be the case. So don't worry about that. I think it is OK, and since you say it works after changing the name back you're good.
I am a bit confused that the file has a 12/4 date on it. I can tell you that file dates get confusing because when you create a backup, prior backups in the chain can get modified. 12/4 is not on your weekly backup schedule so not sure what happened on that day.
I don't know if this will work, but might be worth a try...
Copy the 12/10 version to another folder and give it a completely separate name, e.g. "Samsung 12-10 Copy.tibx". Then see what happens if you use Acronis to "Add existing backup" for that copy. It might load it up as something completely disassociated with the regular backup chain.