Call “VirtualMachine.Relocate” for object “VM-NAME” on vCenter Server “vCenter-Name” failed or The method is disabled by ‘_DP-EPA_BACKUP_RESTORE_LOCK_’


Error: Call “VirtualMachine.Relocate” for object “VM-NAME” on vCenter Server “vCenter-Name” failed or The method is disabled by ‘_DP-EPA_BACKUP_RESTORE_LOCK_’
Symptoms
•    Storage vMotion fails
•    In vCenter Server 5.0, the Migrate option is grayed out
•    Cannot drag and drop a VM from one folder to another
•    Unable to move VM between folders
•    Cannot move Virtual Machine between folders.
•    The Remove from Inventory option may be greyed out for the VM
•    In the vSphere Client, you see the error:
•   The method is disabled by ‘_DP-VEPA_BACKUP_RESTORE_LOCK_’

This problem may occur when the backup job completes but the entry was not removed in the DB.

Error Stack
Call “VirtualMachine.Relocate” for object “VM-NAME” on vCenter Server “vCenter-Name” failed

•  The method is disabled by ‘SYMC-INCR dd-mm-yyyy hh:mm’

Error Stack
Call “VirtualMachine.Relocate” for object “VM-NAME” on vCenter Server “vCenter-Name” failed
•    The method is disabled by ‘Data Recovery’

•    A pop-up message similar to the following may occur when you start storage vMotion

Invalid / explicitly disabled state operation is invoked

Cause:
This issue occurs because the entries from VPX_DISABLED_METHODS are not removed after a virtual machine backup task completes. When a VM-level backup begins, the backup system informs vCenter to disable Storage vMotion for that VM to ensure that the backups can complete successfully. If no backups are active for that VM when this error occurs, Storage vMotion did not get re-enabled automatically.

Resolution:

To workaround this issue:
1.    Power off the virtual machine.
2.    In the vSphere Client, right-click the virtual machine and click Remove from Inventory.
3.    Browse to the datastore where the virtual machine resides.
4.    Right-click the .vmx file of the virtual machine and click Add to Inventory. This gives the virtual machine a new ID.
5.    Power on the virtual machine and retry the Storage vMotion.

As an alternative workaround, you can manually remove the entries from the vCenter Server database:

1.    Stop the vCenter Services.
2.    Take a backup of the vCenter Server database.
3.    Run this command against the vCenter Server database.

select * from VPX_VM WHERE FILE_NAME LIKE ‘%Virtual-Machine-Name%’

4.Take note of the numerical ID value returned by the above SQL stmt, as this will be required in the SQL stmt in steps 5 and 6.

5.Run this command against the vCenter Server database, to confirm the stale entry:

select * from VPX_DISABLED_METHODS WHERE ENTITY_MO_ID_VAL = ‘vm-<ID from step 4>’

6.To remove the stale entry run this command against the vCenter Server database:

delete from VPX_DISABLED_METHODS WHERE ENTITY_MO_ID_VAL = ‘vm-<ID from step 4>’

7.    Start vCenter Server Services, then retry the Storage vMotion.

Ref: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2008957

Advertisements

One Response to Call “VirtualMachine.Relocate” for object “VM-NAME” on vCenter Server “vCenter-Name” failed or The method is disabled by ‘_DP-EPA_BACKUP_RESTORE_LOCK_’

  1. Pingback: ballet leotards

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: