#1 Global Leader in Data Resilience

Cannot edit configuration of VMware VM via ESXi after Instant Recovery from Veeam Agent backup

KB ID: 3155
Product: Veeam Backup & Replication
Veeam Agent for Microsoft Windows
Veeam Agent for Linux
Version: Any
Published: 2020-04-24
Last Modified: 2020-08-13
mailbox
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

When you complete Instant VM Recovery from the Veeam Agent backup, then try to edit the VM configuration via ESXi, the following error occurs:
"Enter a disk size which is larger than its original capacity."

Then you try to edit the decimal virtual disk size via ESXi, and another error occurs:
"Failed to reconfigure virtual machine %VM_name%. Invalid operation for device '%device_number.'"

When you try to edit the decimal virtual disk size via vCenter, no error occurs.

Cause

Instant recovery of physical servers does not round up the size of the disk by design. That is why Veeam Backup & Replication might create virtual disks with decimal sizes. If you perform Quick Migration after the recovery, the disks will remain decimal. Due to the VMware bug, ESXi cannot edit the VM configuration with the decimal disk size.

Solution

If you have vCenter, use it as a workaround to successfully edit the VM configuration.

If you do not have vCenter, you need to extend each decimal virtual disk size manually via vmkfstools:
  1. Connect to ESXi that hosts the VM, then go to the VM directory: cd/vmfs/volumes/%datastore_name%/%VM_name%/.
  2. Keep in mind the name of the VMDK file which size you want to increase. Please, ensure that you run the command below on the VMDK file and NOT on the FLAT-VMDK file or the SESPARSE file.Run the following command: 
    vmkfstools -X NGB %VM_name%.vmdk
    where "N" is the rounded-up value (for example, if the virtual disk size is shown as 59,5123213218GB, then enter 60GB).
  3. Remove the VM from the inventory, and re-register it.

More Information

To learn more about extending a virtual disk with vmkfstools, see this VMware Docs article.
To submit feedback regarding this article, please click this link: 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 hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

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 hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
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.