ASR initial copy only works on one host in Hyper-V cluster

Question

Azure site recovery initial copy only works on one host in the Windows Fail Over Cluster. Once the initial copy is complete I can live migrate the VM to any other host in the cluster and it will continue to replicate delta changes from then on.

On any other host in the cluster the initial copy fails almost immediately and we get a connectivity error in the CBEngine log:
42B0 42CC 03/22 11:58:38.805 79 WcfClient.cs(998) CD9B4F56-7C64-49EA-B84D-73827D6CB773 D947EC2E-8A9F-42EA-8FD4-B3B7317417A5 WARNING Unable to make web service call | Params: {Exception: = System.ServiceModel.Dispatcher.NetDispatcherFaultException: The formatter threw an exception while trying to deserialize the message: There was an error while trying to deserialize parameter http://tempuri.org/:CreateSyncSessionResult. The InnerException message was 'Error in line 1 position 513. Element 'http://windowscloudbackup.com/Protection/V2011_09:VhdSnapshotBlobInfo' contains data from a type that maps to the name 'http://windowscloudbackup.com/Protection/V2011_09:VhdSnapshotBlobInfo_V2019_08'. The deserializer has no knowledge of any type that maps to this name. Consider using a DataContractResolver if you are using DataContractSerializer or add the type corresponding to 'VhdSnapshotBlobInfo_V2019_08' to the list of known types - for example, by using the KnownTypeAttribute attribute or by adding it to the list of known types passed to the serializer.'. Please see InnerException for more details. ---> System.Runtime.Serialization.SerializationException: Error in line 1 position 513. Element 'http://windowscloudbackup.com/Protection/V2011_09:VhdSnapshotBlobInfo' contains data from a type that maps to the name 'http://windowscloudbackup.com/Protection/V2011_09:VhdSnapshotBlobInfo_V2019_08'. The deserializer has no knowledge of any type that maps to this name. Consider using a DataContractResolver if you are using DataContractSerializer or add the type corresponding to 'VhdSnapshotBlobInfo_V2019_08' to the list of known types - for example, by using the KnownTypeAttribute attribute or by adding it to the list of known types passed to the serializer.

All the hosts have the latest agent installed and otherwise setup the same.

Answer 1

@Alex Harwood Appreciate your patience in this matter!

As per support case the issue is now resolved.

"Sharing the solution with broader community"

To resolve this issue, support team performed the following steps:

1. Uninstalled the current MARS agent from control panel on the faulty servers
2. Downloaded the appropriate MARS agent that matches the provider version. Can be downloaded from this link - Update rollup 61 for Azure Site Recovery -KB5012960
3. Installed the MARS agent and enabled protection for the virtual machines - Successful.

Hope this helps!

----------------------------------------------------------------------------------------------------------------------

If the response helped, do "Accept Answer" and up-vote it