Instant Recovery or Multi-OS File Level Recovery fails when the VM has Flex-SE disk

KB ID: 2031
Product: Veeam Backup & Replication
Version: All
Published: 2015-05-04
Last Modified: 2020-08-13
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.

Challenge

Even if there is at least one manually created SEsparse (Flex-SE) disk attached to the VM in backup you will experience the following issues:
  1. A File Level Restore from Other OS session fails with the error:
“Failed to mount restore point
PowerOn failed
File
/vmfs/%vPower NFS datastore%/%sesparse-disk%.vmdk was not found”

User-added image

 
  1. An Instant VM recovery fails with the error:
 
“Failed to publish VM. Error: The file specified is not a virtual disk”

User-added image

Cause

Manually created SE Sparse (Flex-SE) disks are not supported for publishing on the NFS datastore.

Solution

Workaround 1: Exclude these disks from future backups.
Workaround 2: Restore whole VMDK files using “VM Files restore” feature and attach them to another machine to get access to the file system. Please note, that you can attach such disks only in VMWare VSphere Web Client and the VM Hardware level should be at least 9.

More information

To check your disks type open “Edit Settings” in VM Hardware section at Summary tab of your VM in VMWare VSPhere Web Client. If type is shown as Flex-SE then your VM is using SEsparse disk(s).
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.