24.09.2015 · Re: There is no FIB [summary.xml] in the specified restore point Post by wishr » Thu Nov 15, 2018 10:14 am this post Please also note, that for each case the root cause could be different, that's why we require all the logs and additional information on each case.
Jan 24, 2012 · 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.
16.07.2013 · 2015-03-17 23:36:31 :: Processing xxxx Error: There is no FIB [summary.xml] in the specified restore point. Failed to restore file from local backup. VFS link: [summary.xml].
Aug 17, 2012 · Re: Error: no FIB [xxx.vmdk] in the specified restore point. If your job was created at the time when the product had this bug (versions 6.0 or 6.1), then the issue may surface even with the latest version of the code. In this case, performing Active Full once will fix it once and for all.
23.01.2012 · 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.
Jun 20, 2013 · A backup job to a repository with an unstable connection may throw the error “There is no FIB [summary.xml] in the specified restore point” error.
10.03.2018 · 03.10.2018 14:51:40 :: Processing SERVER-DB Error: There is no FIB [summary.xml] in the specified restore point. Failed to restore file from local backup. VFS link: [summary.xml].
29.04.2013 · Re: Error: no FIB [xxx.vmdk] in the specified restore point. If your job was created at the time when the product had this bug (versions 6.0 or 6.1), then the issue may surface even with the latest version of the code. In this case, performing Active Full once will fix it once and for all.
Jul 16, 2013 · 2015-03-17 23:36:31 :: Processing xxxx Error: There is no FIB [summary.xml] in the specified restore point. Failed to restore file from local backup. VFS link: [summary.xml].
Veeam Backup & Replication will “forget” these restore points and not ... only the selected restore point and restore points that depend on it (a part of ...
22.03.2016 · Full backup file merge failed Error: There is no FIB [summary.xml] in the specified restore point. Failed to restore file from local backup. VFS link: [summary.xml]. ...
20.06.2013 · It is possible that using an advanced procedure, Veeam Support may be able to manually generate the missing summary.xml and insert it into the restore point to repair the file. However, most often, the issue that has caused the software not to write the summary.xml into the restore point will have also corrupted the restore point.
Is the failure to create a restore point on this run not critical to success of the overall job? Is this creating a new baseline? If so why is this not a ...
Sep 24, 2015 · Re: There is no FIB [summary.xml] in the specified restore point Post by wishr » Thu Nov 15, 2018 10:14 am this post Please also note, that for each case the root cause could be different, that's why we require all the logs and additional information on each case.