Failed to lock file on VM PowerOn (SureBackup\Instant Recovery)

KB ID: 1942
Product: Veeam Backup & Replication
Version: 6.x, 7.x
Published: 2014-10-29
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

SureBackup or Instant VM Recovery fails with an error relating to failure to power on.
 
The SureBackup log file contains the following error:

 
Info     [VimApi] PowerOffVM, type "VirtualMachine", ref "vm-xxxx"
Error    SureBackup operation has been failed  
Info     [VimApi] PowerOffVM, type "VirtualMachine", ref "vm-xxxx"
Error    SureBackup operation has been failed  
Error    Failed to lock the file

Cause

The following are the two most common causes of this issue:
  1. ​A disk exclusion has been configured in the job, but the “Remove excluded disks from VM configuration” option was not enabled when the job ran. Causing the references to those disks to have not been removed from the backed up VM’s VMX.
  2. Disks that are configured as Independent Disks were automatically excluded by the job, but the job needs to be configured to exclude them manually and have the “Remove excluded disks from VM configuration” option enabled.

Solution

If any disks are configured to be excluded the “Remove excluded disks from VM configuration” option must be enabled within the disk exclusions section for the backup job. Any disk that is configured on the VM as Independent must be excluded from the job, and the “Remove excluded disks from VM configuration” option enabled.
 
http://helpcenter.veeam.com/backup/70/vsphere/backup_job_excludes_vm.html

More Information

If the issue persists after having properly configured the backup job, the ‘ItemsCache’ for the vPower NFS Server may need to be cleaned up. 

To do this remove all keys except 41 from HKLM\Software\Wow6432Node\VeeamNFS\ItemsCache

Then restart the server acting as the vPower NFS Server.

User-added image

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