Calculating digests like crazy

VMware specific discussions

Calculating digests like crazy

Veeam Logoby frigomiam » Tue Jul 11, 2017 1:54 pm

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,
frigomiam
Enthusiast
 
Posts: 34
Liked: 4 times
Joined: Tue Nov 25, 2014 3:47 pm
Full Name: francois nature

Re: Calculating digests like crazy

Veeam Logoby DGrinev » Tue Jul 11, 2017 4:08 pm

Hi Francois,

frigomiam wrote: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.
DGrinev
Veeam Software
 
Posts: 378
Liked: 47 times
Joined: Thu Dec 01, 2016 3:49 pm
Full Name: Dmitry Grinev

Re: Calculating digests like crazy

Veeam Logoby frigomiam » Wed Jul 12, 2017 9:45 am

thank you Dmitry, that makes sense
frigomiam
Enthusiast
 
Posts: 34
Liked: 4 times
Joined: Tue Nov 25, 2014 3:47 pm
Full Name: francois nature


Return to VMware vSphere



Who is online

Users browsing this forum: No registered users and 15 guests