Duplicate VMDK UUIDs are created when virtual machines are deployed from a template (2006865)
- Virtual Machines have duplicate virtual disk (VMDK) ddb (disk data base) UUIDs
- Backup software fails
- You receive a message in the vSphere client similar to:
"/vmfs/volumes/DATASTORE/VM_FOLDER/VM_NAME.vmdk" and "/vmfs/volumes/DATASTORE/VM_FOLDER/VM_NAME2.vmdk" have the same UUID. Virtual disks with the same UUID should not be assigned to a virtual machine because duplications can lead to problems when the guest boots. Make sure the virtual disks have unique UUIDs.
- The virtual machine fails to power on and gets stuck at 95% in progress
This article describes a specific issue. If you experience all of the above symptoms, consult the sections below. If you experience some but not all of these symptoms, your issue is not related to this article. Search for your symptoms in the Knowledge Base or open a Support Request.
To work around this issue, deploy virtual machines to the same host and then migrate them later. This ensures that each disk has a unique identifier.
If you have already identified the virtual machines with the same UUID, run this command to change the ddb UUID: