To shed some light on this error:
- Code: Select all
There is no FIB [summary.xml] in the specified restore point.
The mentioned 'storage failure' was caused by the fact that two different jobs - backup and replication of the same VM - were pointed to the same repository server and replication job was set up to get seed from the same repository where the first job stores its backup. This caused a conflict and resulted in some corrupt record in Veeam DB and a corrupt chain for the backup job, which could be worked around by rerunning the full backup.
This specific issue was addressed in v6.1 meaning that such setup should not lead to corruption anymore (but obviously already corrupt chains cannot be fixed without running the full backup, as backup data in repository is not valid).
However, now we have a couple of cases where this error showed up on a job created in v6.1, most probably due to some other reason. These are being investigated at the moment.