1-800-691-1991 | 9am - 8pm ET
EN

CID Mismatch in VMware on Restore with Backup and Replication V9 installed on Server 2008R2

KB ID: 2187
Product: Veeam Backup & Replication
Version: 9.x
Published: 2016-11-09
Last Modified: 2020-08-13

Challenge

Upon restore using Veeam Backup and Replication V9X you receive a CID mismatch error when you are on vSphere 5.5 Update 3b

Cause

This is a known issue with restoring with the option to use VM tags is enabled in vSphere 5.5 Update 3b

Solution

Known workarounds:
  1. Upgrade Backup and Replication server to Windows 2012 or 2012R2
  2. Deselect 'Restore VM tags'
  3. Disable the following regkey https://technet.microsoft.com/en-us/library/dn786418(v=ws.11).aspx#BKMK_SchannelTR_ClientCacheTime
KB ID: 2187
Product: Veeam Backup & Replication
Version: 9.x
Published: 2016-11-09
Last Modified: 2020-08-13

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

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Your report was sent to the responsible team. Our representative will contact you by email you provided.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Policy.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you for your interest in Veeam products!
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.

OK

error icon

Oops! Something went wrong.

Please try again later.