Calculating digests like crazy

[frigomiam]

Hi,

I had 1 replication job configured with 1 destination ESX in my DR. It was working ok.
I did a manual migration of a VM to another datastore. Then the job started to fail as it couldn't find the vmref.
I realize it was because the job was configured with the ESX not vCenter. That's fine.

I change the job and point it to ESX in vCenter inventory instead, then remap all seeding replicas in the job..

When I start the job, all vm in the job needs requires a Calculating digests abd that's an issue because it's taking ages..

=> Why does it have to calculate digets when the disks and replicas haven't changed ?
=> Was it possible to not fall into this situation ?

Thank you,

[DGrinev]

Hi Francois,

Why does it have to calculate digets when the disks and replicas haven't changed ?

Since you've changed management of VMs in the job to vCenter all VMs got new morefIDs, in this case they appear like a new machines (Veeam B&R doesn't know if it is the same VMs).
That's why digest calculation has been started to compare differences between previously used VMs and "new ones".

Managing virtual infrastructure by vCenter is highly recommended approach that would allow you to avoid such situations in the future.

[frigomiam]

thank you Dmitry, that makes sense

[ortoscale]

Hi there,

I've moved esxi host + nas with existing replicas to remote location (ip change , remove from vcenter, register replicas again)
then install veeam proxy at remote location
configure replica seeding with mapping
and run replication job

but it's taking forever with digest, can we avoid calculating digest in any way (metadata stays on same location on source) ?

thanks

[DGrinev]

Hi Matjaž,

Since you've changed the management of replicas they recognized as never seen before due to new IDs.
Please read this thread for additional information. Thanks!

[ortoscale]

Ok thanks. I was suspecting that. Just needed confirmation

[ortoscale]

suddenly got this Preparing replica VM Error: The operation has timed out with on job. Google returns nothing, I checked log files on Veeam server but find nothing useful, not sure whether i should open support case or delete replica and start over for this particular job.

[DGrinev]

Hi Matjaž,

I'd recommend you to open the support case and let them take a closer look at the logs.
Also, you can post the case ID number here, so we can track it too. Thanks!