Cluster replication issues (network mapping)

[dlapointe]

I am currently facing a "major" issue using Veeam replica on a Hyper-V cluster. I am still working on this with support team but here's the situation:

We have VMs on Hyper-V cluster "A" which replicate to Hyper-V cluster "B". The replica job is configured for network mapping (Select source VLAN and Target VLAN).

However, the replicated VMs will only have the proper VLAN target tagger if they are on a specific Hyper-V Host.

Here's what I mean:
Our hyper-v cluster "B" have 4 hosts/nodes, if the replica is not on the specific node "2" of the cluster, than the target VLAN tagging will not work properly and will still tag the source VLAN. However, if the replica VMs is on the node "2", the target VLAN is properly tagged.

This is causing issues while trying to failover the VMs since they do not have the proper network configured..

After digging the issue and reviewing our hyper-v cluster networking config, I found the issue within Veeam:

In Veeam&Backup replication GUI, While you select the logicalswitch of the target network of a cluster, it only offers you a default choice (which is the name of your logical switch). I suspect it is selecting a switchID of a random host/node within the cluster because in veeam database, I found out that in the replication job setting, the "targetswitch" name is identified for the switchID of the host itself and not the whole cluster. which explain why the replica's get proper VLAN tagged only on this specific host.

So for now, the "failover" scenario works out if you only have a single hyper-v host for the replicated VMs.. Still wondering if there's the same issue with VMware

[Mike Resseler]

Hey Dominic,

Could you please add your support case for this thread?

Thanks
Mike

[dlapointe]

Hi Mike,

My support Case is # 03399797

[Mike Resseler]

Thanks Dominic,

I see you have been working with our support, but that you can't upgrade because some integration would break. Are you on U1?

In the meantime I will talk with our Microsoft specialists internally.

[dlapointe]

Hi Mike,

Yes, for that specific instance, we cannot upgrade it and we are stuck on version 9.5.0.1038

We are also suffering same issue on version 9.5.0.1922 on another veeam server.

However,

We have few more veeam environment which we can upgrade. I was able to upgrade it yesterday and I am working on replications jobs now on U4.

[dlapointe]

At first look, it seems to be working fine on Update 4

[dlapointe]

Confirmed fixed in U4 FYI.

[Mike Resseler]

Thanks Dominic,

I hope you can upgrade all of your environments to U4 as soon as possible

Cheers
Mike