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:
Last Modified:
2015-05-04

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).

Please be aware that we’re making changes which will restrict access to product updates for users without an active contract.

OK

Rate the quality of this KB article: 
5 out of 5 based on 1 ratings

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:

Submit