Every now and then, when creating an iTunes backup, it can turn out to be corrupt, sometimes without realising it until trying to restore. Error messages shown in iTunes for a corrupt backup can vary depending on the main issue, sometimes without giving us any clues on the real problem.
In most instances, it’s almost impossible to repair corrupt backups, and certainly not without a full understanding of what is missing and how to fix it. The next best option is the recovery of data and files that still exist, by simply using the Free version of the iPhone Backup Extractor that can show what data is in a backup.
If an error message is received when loading the backup in the iPhone Backup Extractor, like
Error loading backup in .... Not a valid mbdb
Couldn't load backup in /Users/Username/Library/Application Support/MobileSync... file opened is not a database file
...there was something wrong with the manifest an underlying SQL exception occurred
AuthData Value was not a dictionary/node
Don't despair just yet, we might still be able to help with the data recovery.
Corrupted manifest files is a case for our support team.We will need to analyze the
status.plist files from the backup to see if we can identify and fix the problem.
The files can be attached in a reply for us. Follow this link that explains how to find these files.