https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2I0MDkzIiwiaGFzaCI6IjVjNDAzMTRkLTJmMzktNGQxYi1hNjg4LTU5Mzg2NDY3ODUwNiJ9
1-800-691-1991 | 9am - 8pm ET
EN

Cisco HyperFlex & Veeam CDP support status

Challenge

Cisco HyperFlex VM Snapshot creation process will stop VMs if a Veeam CDP storage policy filter is present. Affected VMs will not boot anymore.

Cause

The Cisco HyperFlex Snapshot creation process changes the ddb.sidecars entry within the vmdk metadata and reference to a non existing vmfd file.

Solution

  • Make sure that the VM is in shutdown mode.
  • Go to the Veeam Files Area within Backup & Replication and browse to the base folder of the VM.
  • Select the <vmname>.vmdk file and right-click “edit”
  • Go to the ddb.sidecars entry and correct the vmfd filename so that it points to the existing file within the same folder.
Example:
VM Name: Sample
vmdf File on disk: Sample-c9c24ae00ec07941.vmfd"
Sample.vmdk file on disk shows: ddb.sidecars = "veecdp_1,Sample_675617-62e8e8ccb585c028.vmfd"
This entry need to be corrected to: ddb.sidecars = "veecdp_1,Sample-c9c24ae00ec07941.vmfd"
  • Save and close the editor.
  • Boot the VM.
KB ID: 4093
Product: Veeam Backup & Replication 11
Published: 2021-02-01
Last Modified: 2021-03-24
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

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

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.

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 go back try again later.