CID mismatch error

[zoltank]

Our production VMware environment is ESX 4.1 which we're backing up with Veeam v.9. We just stood up a new ESXi 5.5U3 environment. However, when we tried to restore a VM into it we received a CID mismatch error and the VM wouldn't start up. However, we found when we unchecked "Restore VM Tags" the restored VM would start up without problem.

Could someone please explain to me why this is happening?

[nielsengelen]

It might be related to the fact that there are no tags in ESX 4.1 and this fails because of that reason. Even though I advise you to contact support as this might be a bug.

[zoltank]

I went ahead and opened a case, #01805288.

I don't mind just unchecking "restore VM tags", but I want to make sure there isn't another issue which might bite me later.

[nielsengelen]

Normally it shouldn't. Tags are available in 5.5 so once a backup is made it won't give the error anymore (even if you aren't using tags).

[zoltank]

I’ve restored several VMs now, and it seems to be consistent that if I restore the tags then I get the CID mismatch, and if I don’t then it works fine. The ESXi 5.5U3 environment that I’m restoring into has a vCenter server, which is what I’m using as my target in Veeam.

To test things, I took another server identical to the ones in the 5.5 environment and did a test restore to it, both with and without tags. Both VMs powered up without issue. However, that was a standalone and did not have a vCenter server.

[Uniko]

Hi All,

we are facing the same issue and we can confirm that the workaround recommended by zoltank works fine.

We' re working with Vpshere 5.5 U2 and VEEAM 9.0.0.902.

An official explanation about this behavior will be appreciated.

Kind Regards,
Davide

[veremin]

Just to verify - you'd backed up VM residing on a host/cluster running vSphere 5.5, when you tried to restore such VM with "restore VM tags" option enabled, you got CID mismatch error, right? Thanks.

[Uniko]

Exactly...

[veremin]

Kindly, open a ticket with our support team and let them fix the experienced behaviour.

Refer to the ticket #01805288 in order to speed up investigation. It seems that our engineers are currently working with VMware team on addressing this issue.

However, there appears to be a regkey allowing you to solve the problem - ask support team to provide you with it.

Thanks.