v12 upgrade / duplicate disk IDs & hotadd failures

[eblack]

Case#06034094

We updated from 11a -> 12. After bringing everything online we experienced a lot of failures on hotadd due to dupe disk IDs. We've been able to mitigate the VM portion with switching to network transport for now. The Hyper-V however is still an issue. Here's what's presenting in the CC job session logs. Nothing was changed other than the v12 update. Any thoughts on correcting it are appreciated.

[HvSnapReplicaDiscover] Replica marker job ID '9f8e98c7-cb1a-40d6-b9db-559a1ea99ce2' is different from current job ID 'a42e2710-7a6e-4f6f-9c11-f39facc1d39f'
<262> Info         [HvSnapReplicaDiscover] Failed to check replica marker

&

value="8bb4847f-ed13-45d1-97ec-084f034692d5" /></InputArguments>
Selected vm doest not belong to this tenant (System.Exception)

[Mildur]

Hi Eric

HotAdd is a transport mode for vSphere Backups, not HyperV.
In vSphere, duplicated disk uuids are not supported in v12. They were never supported by VmWare. VmWare confirmed duplicated uuids as an known issue in one of their kb articles.

Please keep working with our support team on this issue for HyperV. Such issues cannot be solved over the forum. It also doesn‘t seem to be related to duplicated uuid from vSphere.

Best,
Fabian

PS:
Please register yourself in our service provider user group. This gives you access to our hidden service provider sub forums where service provider products are discussed: Apply for the Cloud and Service Providers user group

[eblack]

Thanks for the response. Can you clarify what changed? I understand this is a result vs cause. Is it just scrutinizing the IDs better now?

[Mildur]

Let's discuss the VmWare issue in our other topic. This one should only be used for your HyperV issue.

VmWare duplicated UUID topic:
vmware-vsphere-f24/problems-with-vcente ... 85591.html

To solve the issue on VmWare side, you can use KBs from VmWare:
https://kb.vmware.com/s/article/1021189
https://kb.vmware.com/s/article/2006865

I will update the other topic once I have information from our QA team what we have changed.

Best,
Fabian