https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IxNjY5IiwiaGFzaCI6ImY3YTY0NzBmLWRhOTItNGZjOS05OTJiLTIyM2QyM2MzZDg0NSJ9
1-800-691-1991 | 9am - 8pm ET
EN

"VM MAC address conflict" and "VM instance UUID conflict" alarms

Challenge

During replication jobs, Veeam ONE triggers the VM MAC address conflict and VM instance UUID conflict alarms.

Cause

When a VM replica is created, it acquires the same MAC address and UUID as the original VM. This situation is normal because a newly created replica is an absolute copy of the original VM with exactly the same properties.
After a short time, VMware vSphere changes replica’s MAC address and UUID.

Solution

This behavior is by design. However, if you do not want to receive the alarms, disable the VM MAC address conflict and VM instance UUID conflict alarms for source VMs or for the target location.

More information

If you have any questions or problems, please contact Veeam Support at http://www.veeam.com/support
KB ID:
1669
Product:
Veeam ONE
Version:
6.x - 9.x
Published:
2012-10-01
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later