Veeam 9.0 - Snapshot Merge Timeout

[L33T]

HI,

Since upgrading to v 9.0 i have noticed that we get timeouts on the replication job when the vm`s are merging snapshots. The vm`s do complete merging successfully but the job itself error`s on what appears to be a timeout waiting for that process complete. Our SAN that the replicated vm`s sit on is slow and we are aware it takes time to process but can this timeout limit be changed?

Cheers,

[foggy]

Could you please contact support with this and share your case ID here? To understand whether there's a timeout that might help in this case, we need to review the log files. Thanks.

[L33T]

Done Foggy Case ID 01989337

[hobensovbr]

Dear all,

Just a question regarding replication job timeout values for Hyper-V.

I have a replication job that runs once a day, however the job sometimes fails with the error:
"Failed to apply retention policy for VM: VM_replica Error: The operation has timed out."

This seems to happen because backend Hyper-V checkpoint merge takes longer than the 1 hour limit to complete.

My question is. Is it possible to increase this time out to say 2 hours to allow the merge time to complete?
I have checked in the registry on the backup and replication server, however nothing obvious to change in there.

Any help would be appreciated.

Kind regards,
Ben Holland

[foggy]

Hi Ben, I appreciate if you open a case with technical support regarding this issue. Thanks.

[hobensovbr]

Thanks for getting back to me.
I have logged a support ticket and the case number is 01994859.

I will update this forum with the results.

Thanks,
Ben

[hobensovbr]

Ok support have got back to me.
They have suggested that I add the following registry key to HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication

HyperVDefaultWMITimeoutSec
Type: REG_DWORD
Default value: 3600 (decimal, seconds) - I have changed the default value to 10800 (3 hours).

I have also rebooted the B&R server just to make sure.

The replication job runs overnight so I will post back tomorrow with the results.

Thanks,
Ben

[L33T]

How did it go with the reg change? Support still havent got back to me about this, been a while!

[foggy]

I can see that your case was closed due to no response from your side. You can re-open it, if you'd like further investigation.

[L33T]

We did respond to this foggy, didn't hear back from alexander at the time sorry.

This reg fix also worked for us, quite happily waits for the merge to complete on the jobs...

Cheers,