Forcing digest recalculation and comparison?

[gglynn]

Due to some underlying infrastructure problems that required me to move around some replicas and delete snapshots, I have a handful of 4TB VM replicas whose metadata I'm not confident matches what's in Veeam's configuration databases at present. What's the easiest way for me to trigger digest recalculations and comparisons on the existing replication jobs for them so I can ensure that I've got consistent disk states between source and target? I can't do a full re-replication (it'll cost a fortune in datacenter transfer fees), and I'd rather not modify the existing jobs much if I can help it. I already tried rescanning the replicas and disabling CBT on the jobs, and while it appears to be scanning every block of the source disks again based on how long it's taking, there's no explicit mention of digest calculation in the job status log messages, which concerns me.

[vnikiforov]

Hello, George,

Neither step you tried reaches the digests. Rescan Replicas only refreshes the replica and restore point records in the configuration database. With CBT disabled, the source proxy reads every source block and compares it against the replica metadata already stored in the repository. The replica disks are never read, so a full scan on the source side says nothing about the target, and that is why the log shows no Calculating digests step.

With that said in your particular case I strongly recommend to open a support case and attach full logs, I see several known issue related to replicas and digest in the latest version, so that must be first analyzed before any actions.