I just wanted to chime in and bump this. I have decided to just start with recreating the bkp copy job. I am on v. 8.0.0.2030 and got the FIB error. Mostly just an FYI rather than a request for input. Just thought someone might be interested to know it's still occurring.
9/24/2015 12:50:11 AM :: Error: There is no FIB [summary.xml] in the specified restore point.
Failed to restore file from local backup. VFS link: [summary.xml]. Target file: [MemFs://frontend::CDataTransferCommandSet::RestoreText_{46e79f52-6017-4b6b-8b88-2e36a16b5065}]. CHMOD mask: [0].
Agent failed to process method {DataTransfer.RestoreText}.
We are getting this error on a backup copy job that has been working fine since it was set up in April. The job has three VM's, one VM is processed successfully and and two fail.
The full error we are getting is:
There is no FIB [summary.xml] in the specified restore point.
Failed to restore file from local backup. VFS link: [summary.xml]. Target file: [MemFs://frontend::CDataTransferCommandSet::RestoreText_{9faee25a-9a63-4df3-8912-7fdd54064a2a}]. CHMOD mask: [37353276].
Agent failed to process method {DataTransfer.RestoreText}.
We have discovered it is only happening with one of two USB drives that are rotated, using the same copy job.
The drive that has the problem has 189GB free where as the one that works has over 1TB free. Could the be disk space related? The drives are the same size and have the same retention period as they use the same copy job so I would expect them to have the same amount of free space? If you think that it is disk space related? I've tried lowering on re-retention but it hasn't freed up any space, can I manually delete file on the drive?
Thanks for the reply foggy.
I've had a case open with support for two days now and not had any reply from them despite requesting an update.
Comparing the number of files on each USB drive the one with the problem has 133 files and the one that working fine has 110. However I don't think the retention period is working on the copy job as it shows .vib files going all the way back to April when the job was setup. I tried lowering the retention period of the copy job last week when we started having the problem but hasn't freed up any space.
Getting the FIB error on a backup copy job too, last version.
I'll make a SR (edit : SR 01255967 ) and let your know.
That might be because I did not format my repository using "large NTFS File Record Segment (FRS)" but I had another repository without FRS and I got the large FRS specific error wheareas here I only get this FIB error.
And If I could correct this error without having to move / format / move that would be cool.
28/12/2015 14:25:43 :: Failed to perform backup file verification
28/12/2015 14:29:42 :: Processing ged2 Error: There is no FIB [summary.xml] in the specified restore point.
Failed to restore file from local backup. VFS link: [summary.xml]. Target file: [MemFs://frontend::CDataTransferCommandSet::RestoreText_{7ead4f82-7d06-40dc-ada8-10357e344edd}]. CHMOD mask: [0].
Agent failed to process method {DataTransfer.RestoreText}.
How did you do it ?
It was a bug with regular backups or backup copy jobs ?
You deleted from the regular backup repository or both ?
You used the "Backups->Disk->right click on VM->Delete from disk" menu ?
I am getting the "There is no FIB" error on a backup copy job as well, however it only happens on the 2nd backup copy job. Using v9 with the latest update, I have the job chain setup this way:
- Regular backup job (incremental with weekly synthetic backup, 14 retention points)
- Local Backup copy job based on backup job above (14 restore points, Keep: 4 x Weekly backups, 84 x Monthly restore points) <- this works fine every day
- Remote Backup copy job based on backup job above (14 restore points, Keep: 4 x Weekly backups, 84 x Monthly restore points) <- this fails with the FIB error every day
- The remote backup copy job uses WAN accelerators to move data from site a to site b
Hi
Environment is Veeam 9.5U3 on VBR server and Proxies.
Backup is done locally in remote office to local attached disk as Windows Repo.
Backup is Incrementals with Synthetic Full and Transform into rollbacks.
We save 30 Points
Backup has been working 100% until this weekend where it fail at synthetic full with the below error, next incremental is OK
Previous full backup chain transformation failed Error: There is no FIB [summary.xml] in the specified restore point.
Referring to kb1778 I need to do a new Active Full backup to solve the situation, no problem but is the chain with 30 restore Points corrupt and unusable?
I will schedule an Active full for tonight but still worried about the previous backups
Do not delete or modify existing restore points. Instead, please open the case, support team should be able to identity whats going on with the hand of your Veeam B&R debug logs. Please do not forget to include the case ID in this thread. Cheers!
I'm having the same problem in a similar setup.
The first time the issue occured was last week. This weekend, a new full backup was performed, but the issue still persists.
What can we do to solve this problem ?
Welcome to Veeam community forums and thank you for the question.
Please note, that according to Veeam forum rules, you should include support case ID when posting about any technical issue, as requested when you click the "New topic" button. Please reach out our support team for extensive investigation and post your case ID here - we'll keep an eye on it.
This is happening to me also....quite all of the sudden.
Is there a resolution or is veeam just pushing to support just like the millions of customer email account leak where veeam just kept quiet and then push to elsewhere ?
For each issue, we require to perform at least basic info collection, then do the analysis in order to offer an appropriate solution. This initial step is done on the support team end. If somebody will be glad to post their case ID we'll be able to assist from the product management perspective.
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. Just to make sure a solution we offer will work in your particular situation.
Same issue here.
case ID# 03597797 and forgot that I have it opened. opened another one a few days ago ID# 03597797
Only/always answer I've got is to run active full. which I did twice.
Unfortunately, since do not know any details, I can only recommend a workaround: delete the latest VBK from the corresponding replica folder on the repository (make sure you have a copy, just in case) and restart your replica job - it will re-calculate all the digests, but in this particular situation, this is the only advice we can share.
Hi Marco, Fedor references the repository that stores replica metadata here, the one you specify in the replication job settings (not the target vSphere datastore where the replica VM resides).
