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.
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.
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.
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.
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 .
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