by B.F. » Fri Mar 04, 2016 2:45 pm people like this post
OK I can try that. Maybe a Veeam feature request would be that Veeam changes the replica's MAC before it completes somehow in midstream? (If that is even possible.) It sounds like vSphere is able to check the replica MAC before Veeam has a chance to make the change.
by B.F. » Fri Mar 04, 2016 3:29 pm people like this post
Don't know if this helps but we have a large VM that takes quite a while for the snapshot to be removed after replication is completed. I'm now seeing a replica of that VM with no alarms triggered while it's in "Remove snapshot" mode. I'm assuming as soon as it's done, the alarm with be triggered.
by Vitaliy S. » Fri Mar 04, 2016 4:14 pm people like this post
B.F. wrote:So MAC changes to the replica is actually done / managed by VMWare? If so, time to pile on VMWare's forums?
When VM replica is created is should be identical to the source VM, after that VMware tries to resolve all conflicts and raises the alarm if it detects some collisions. Maybe there is a way to tweak alarm detection.
by mloeckle » Fri Mar 11, 2016 10:55 pm 6 people like this post
This worked for me. All our replica VMs end with the default suffix "_replica". So I added a Trigger Condition to each of the Alarm Triggers (VM MAC conflict, VM static MAC conflict). Value = "VM name", Operator = "does not end with", and Value = "_replica".