I have couple of questions related to VM UUID
Best answer by Damian Andre
Hey
Commvault does not use the VM GUID as located in the VMX file as it is not guaranteed to be unique. We use the UUID provided by vCenter (known as instanceUUID as well), and that is how VMs are matched and tracked as they move between hosts, get renamed etc.
Where you don’t see a match, make sure its not the VM GUID you are looking at.
In the case of a windows VM, here is some powershell code to show the instance UUID:
([guid]((Get-WmiObject win32_bios).SerialNumber -replace "[\s-]","").Substring(6)).ToString()
When restoring, if the UUID already exists as reported by vCenter then a new one will be assigned. This is common when you restore a copy of a VM.
There hasn't really be any issues relating to UUID or GUIDs since the V9 days - things are pretty solid here so I would not expect anything to go wrong. There is code that checks for duplicated, mismatches etc.
I have couple of questions related to VM UUID
Team, Any update on this!
+23Hey
Commvault does not use the VM GUID as located in the VMX file as it is not guaranteed to be unique. We use the UUID provided by vCenter (known as instanceUUID as well), and that is how VMs are matched and tracked as they move between hosts, get renamed etc.
Where you don’t see a match, make sure its not the VM GUID you are looking at.
In the case of a windows VM, here is some powershell code to show the instance UUID:
([guid]((Get-WmiObject win32_bios).SerialNumber -replace "[\s-]","").Substring(6)).ToString()
When restoring, if the UUID already exists as reported by vCenter then a new one will be assigned. This is common when you restore a copy of a VM.
There hasn't really be any issues relating to UUID or GUIDs since the V9 days - things are pretty solid here so I would not expect anything to go wrong. There is code that checks for duplicated, mismatches etc.
Hey
Commvault does not use the VM GUID as located in the VMX file as it is not guaranteed to be unique. We use the UUID provided by vCenter (known as instanceUUID as well), and that is how VMs are matched and tracked as they move between hosts, get renamed etc.
Where you don’t see a match, make sure its not the VM GUID you are looking at.
In the case of a windows VM, here is some powershell code to show the instance UUID:
([guid]((Get-WmiObject win32_bios).SerialNumber -replace "[\s-]","").Substring(6)).ToString()
When restoring, if the UUID already exists as reported by vCenter then a new one will be assigned. This is common when you restore a copy of a VM.
There hasn't really be any issues relating to UUID or GUIDs since the V9 days - things are pretty solid here so I would not expect anything to go wrong. There is code that checks for duplicated, mismatches etc.
Thanks Damian,
For example, one vm, on commvault end UUID shows as “50019c63-9741-be7e-5251-f3b449c18cb2 but on the VMware end. it shows as “42019194-xxxxx-xxxx-xxxxxx”, and the uuid is not matching. not sure why
+23Where are you seeing the UUID in Commvault? logs?
I think there is a table app_vminfoprop that might store it - but need to double check
Where are you seeing the UUID in Commvault? logs?
I think there is a table app_vminfoprop that might store it - but need to double check
under VM properties
Thanks Remi, GUID and VMGUID is showing same on our commserve end but on the VM side uuid is showing different?
Hey
Commvault does not use the VM GUID as located in the VMX file as it is not guaranteed to be unique. We use the UUID provided by vCenter (known as instanceUUID as well), and that is how VMs are matched and tracked as they move between hosts, get renamed etc.
Where you don’t see a match, make sure its not the VM GUID you are looking at.
In the case of a windows VM, here is some powershell code to show the instance UUID:
([guid]((Get-WmiObject win32_bios).SerialNumber -replace "[\s-]","").Substring(6)).ToString()
When restoring, if the UUID already exists as reported by vCenter then a new one will be assigned. This is common when you restore a copy of a VM.
There hasn't really be any issues relating to UUID or GUIDs since the V9 days - things are pretty solid here so I would not expect anything to go wrong. There is code that checks for duplicated, mismatches etc.
Thanks Damian,
it looks like our is VC.uuid is the one which commvault pull from the vcenter and we have used API to get the information from commvault.
uuid.bios = "42 07 91 7c 22 6a a4 dc-1d 74 aa 67 65 34 05 75"
vc.uuid = "50 07 3f e7 83 16 26 65-bc d9 c7 c4 f2 8a f1 af"
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
