Restore to VMware Cloud Director fails when vmdk file extensions are missing

KB ID: 4228
Product: Veeam Backup & Replication
Published: 2022-02-08
Last Modified: 2022-02-08
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

Article Applicability
This article is relevant only when a vCloud VM restore fails and the restored disk files are missing their .vmdk file extension.

Challenge

When performing a vCloud VM Restore, the operation fails with the following generic error message:
Restore job failed Error: Error in the application.
Example of error
Take note of how the -flat file that failed to restore is missing its .vmdk file extension.

Cause

The restore fails because the restored files are not recognized as VM disks. When this restore failure occurs, it is because the VM that was backed up has disk files that are missing their .vmdk file extension.

At this time, it is unknown by Veeam Support why the .vmdk file extension could be missing from a production VM. If you experience this restore issue and the VM that was backed up is still present, you are advised to contact VMware Support to request assistance with investigating why the source VM is missing its file extensions.

Solution

The following is a workaround that Veeam Support has developed to allow for the restore of a VM that was backed up and had disks that were missing their .vmdk file extension.

  1. Perform a VM Files Restore, placing the restored files in the destination datastore where needed.
  2. Rename the -flat file to add the .vmdk extension.
  3. Manually register the VM.
  4. Check the VMs settings and confirm that it recognizes the disk files.

 

More information

The current prevailing theory is that this may be related to an invalid template that was used to deploy the VM that was backed up, as often when this failure occurs for one VM, other VMs in the environment have been found to be missing their .vmdk file extensions.
Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Verify your email to continue your product download
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
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.