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

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 .

Thanks!

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

Thanks @Dynamic I missed that error in the message!

Will it work on backup copy job ?  

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:
 

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 .

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

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 

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

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! 

I got word from my Veeam case that this is a known issue and they’re working on a fix in their next build. So hopefully problem gets solved soon! They also linked me a KB about starting a new backup chain https://www.veeam.com/kb1885