Skip to main content
Solved

Active full backup on only one VM in in Backup copy job

  • September 3, 2024
  • 12 comments
  • 1040 views

Forum|alt.badge.img+1

One of my VM is showing  FIB summary.txt issue in backup copy job. I would like to run Active full backup on only this problem VM . But this backup copy job has 20 VMs which i don’t want to run full backup as it will cause issue in wasabi bucket. Copy job goes to wasabi bucket. I know individual full backup can initiated in Backup job, but it is not showing BCJ . Please advise.

Ver 12.1.2

Best answer by Dynamic

Hi @Nikks, i think you have already checked and found the KB1778: There is no FIB [summary.xml] in the specified restore point (veeam.com) - if this is your error, the KB mentioned also to start a new active full. 
If you only want to start a active full of this VM (right click on the last status window > active full) no other VMs would then be processed.

Best, Markus

12 comments

dips
Forum|alt.badge.img+7
  • On the path to Greatness
  • September 3, 2024

Hi @Nikks 

Just to clarify, you want to run an Active Full on one VM. This VM is also part of a Backup Copy Job?


Forum|alt.badge.img+1
  • Author
  • Influencer
  • September 3, 2024

Hi @Nikks 

Just to clarify, you want to run an Active Full on one VM. This VM is also part of a Backup Copy Job?

Yes correct. Backup copy job is having issue .


dips
Forum|alt.badge.img+7
  • On the path to Greatness
  • September 3, 2024

Thanks!

What is the issue it is having? Are there any error messages?


Dynamic
Forum|alt.badge.img+16
  • Veeam Vanguard
  • Answer
  • September 3, 2024

Hi @Nikks, i think you have already checked and found the KB1778: There is no FIB [summary.xml] in the specified restore point (veeam.com) - if this is your error, the KB mentioned also to start a new active full. 
If you only want to start a active full of this VM (right click on the last status window > active full) no other VMs would then be processed.

Best, Markus


dips
Forum|alt.badge.img+7
  • On the path to Greatness
  • September 3, 2024

Thanks @Dynamic I missed that error in the message!


Forum|alt.badge.img+1
  • Author
  • Influencer
  • September 3, 2024

Hi @Nikks, i think you have already checked and found the KB1778: There is no FIB [summary.xml] in the specified restore point (veeam.com) - if this is your error, the KB mentioned also to start a new active full. 
If you only want to start a active full of this VM (right click on the last status window > active full) no other VMs would then be processed.

Best, Markus

Will it work on backup copy job ?  


Dynamic
Forum|alt.badge.img+16
  • Veeam Vanguard
  • September 3, 2024

you have to start an active Full within your primary Backup Job (but only on this particular VM), your Copy Jobs will then start immediately, but only copy the new data of this VM, as all other VMs (and their restore points) are still at the same state/there is no new restore point for these other VMs.

 

For example:
 

 


Forum|alt.badge.img+1
  • Author
  • Influencer
  • September 3, 2024

you have to start an active Full within your primary Backup Job (but only on this particular VM), your Copy Jobs will then start immediately, but only copy the new data of this VM, as all other VMs (and their restore points) are still at the same state/there is no new restore point for these other VMs.

 

For example:
 

 

Thanks. So what i understand is that you cannot start an individual VM full backup in BCJ. But need to start full backup in backup job , and the BCJ then copies full backup or incremental?  There is no issue with primary backup, the FIB error showing only in BCJ with this VM .


Forum|alt.badge.img+1
  • Author
  • Influencer
  • September 4, 2024

you have to start an active Full within your primary Backup Job (but only on this particular VM), your Copy Jobs will then start immediately, but only copy the new data of this VM, as all other VMs (and their restore points) are still at the same state/there is no new restore point for these other VMs.

 

For example:
 

 

Thanks. So what i understand is that you cannot start an individual VM full backup in BCJ. But need to start full backup in backup job , and the BCJ then copies full backup or incremental?  There is no issue with primary backup, the FIB error showing only in BCJ with this VM .

Bump


Dynamic
Forum|alt.badge.img+16
  • Veeam Vanguard
  • September 4, 2024

Hi @Nikks, sorry for late response. Active Full in the primary backup job shouldn’t trigger also an active full on your BCJ. 

But I would give it a try, maybe the active full restore point could also help ob your issue. 
As it’s only on this particular VM, you wouldn’t have that much impact on your Object storage charges. 
 

If it’s not helping, I would go for further log analysis or by contacting the support. 
Cheers, Markus 


  • New Here
  • April 15, 2026

I am having the same issue with a backup copy job going to an S3 bucket. Case 08056157 is open on this. Running an Active Full for the entire copy job seems ridiculous when just a single vm is having the issue. We have jobs that have hundreds of vm’s in them. We have jobs that have massive vm’s in them. Anyone find a better solution


  • New Here
  • August 24, 2026

msbel, are you also getting the error with your S3 storage where a single Increment point has the wrong link ID? And then the fix is to run an Active Full, but you can’t run an Active Full on a backup copy job for just one VM (or maybe you can but the immutability may be blocking it or something else)? 

 

I’m also working on something like that. This is the third time this has happened within the last 6 months for me. About to open a case with support, but if our problems are similar, then that would for sure help my case!