https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IxOTE2IiwiaGFzaCI6ImM5ZWYxODE2LTVkNmEtNDUxMy05MzU3LTMyNGRhZDVlYTI4MSJ9
1-800-691-1991 | 9am - 8pm ET
EN

Storage vMotion of Instant Recovery fails with “The method is disabled by ‘’”

Challenge

When attempting to migrate an Instant Recovery VM to a production datastore using VMware Storage vMotion the following error occurs:

User-added image

The method is disabled by ‘VM_ID’
Call ‘VirtualMachine.Relocate’ for object ‘<VM_Name>’ on vCenter Server ‘<vCenter_Name’ failed.


Solution

To correct this issue please perform the following tasks:

1.  Power down the Guest OS of the instant recovery VM from within the OS.
2.  Remove the Instant Recovery VM from Inventory via vSphere client
3.  Add the Instant Recovery VM to inventory from the Veeambackup_ServerName NFS datastore

Once the VM has been removed and added back into the infrastructure please test the Storage vMotion again.

More information

The following VMware KB article is related: http://kb.vmware.com/kb/2008957

KB ID:
1916
Product:
Veeam Backup & Replication
Version:
7.x
Published:
2014-08-07
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

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

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later