Skip to main content
Question

Error message Backup Copy Job "Failed to perform backup verification Error: Unable to get block digest: block is not initialized. "

  • February 27, 2026
  • 7 comments
  • 44 views

Hello everyone,

For several days now, I have been receiving the following error message during our backup copy job:

“Failed to perform backup verification Error: Unable to get block digest: block is not initialized. Skipped arguments: [0]; Agent failed to process method {Signature.FullRecheckBackup}.”

I performed a full backup, but unfortunately the same error message appeared again. The copy job does not conflict with the backup job.

How can I fix this error?

Thanks in advance!

Version: Backup & Replication 12, Build: 12.3.2.4165

7 comments

lukas.k
Forum|alt.badge.img+13
  • Influencer
  • February 27, 2026

Hi ​@er_mat,

Welcome to the community!

To assist with this we do need a few more information. You have a copy job - what are your source backups (e.g. VM backups from vSphere, Hyper-V etc.)? What is your target repository for the copy job? Have there been any changes in the past days / weeks that could cause this? What Veeam version are you running?

 

In general, we are a community but cannot provide technical support in depth. In this specific case I strongly recommend to open a Veeam support ticket, they can help on a deeper level then we can do.

Anyways, please do not hesitate to update us on the topic, we are always happy to be of assistance.

 

Best regards

Lukas


  • Author
  • New Here
  • March 4, 2026

Hi Lukas, thank you for your response.

The source backup type is a hyper-v-backup. The target is a nas.

There was no changes in the last time.

The Veam-Version: Backup & Replication 12, Build: 12.3.2.4165

What is the meaning of the error-message: “Unable to get block digest: block is not initialized”

“Agent failed to process method {Signature.FullRecheckBackup}.”

Kind regard ermat 


eblack
Forum|alt.badge.img
  • Experienced User
  • March 4, 2026

Have you run a new Active Full yet with the source data?

 

 


lukas.k
Forum|alt.badge.img+13
  • Influencer
  • March 4, 2026

Thank you for the update. I’d recommend to open a Veeam support case to continue here.

 

Please feel free to keep us posted!


kciolek
Forum|alt.badge.img+1
  • Experienced User
  • March 4, 2026

please keep us updated on progess with support!


  • Author
  • New Here
  • March 6, 2026

Have you run a new Active Full yet with the source data?

 

 

Yes but with the next run after the full backup, the error message applies again.


eblack
Forum|alt.badge.img
  • Experienced User
  • March 6, 2026

Have you run a new Active Full yet with the source data?

 

 

Yes but with the next run after the full backup, the error message applies again.

I’d rescan the repo and attempt to clone the job (if you have the ability), then run the Active Full once again.

 

Otherwise I might look into this. 

 

https://helpcenter.veeam.com/docs/vbr/userguide/backup_validator_validate.html?ver=13