VMware Storage vMotion fails with the method is disabled by

VMware Storage vMotion fails with the method is disabled by VM-ID.

In vSphere Client, you see the errors:

The method is disabled by ‘_DP-VEPA_BACKUP_RESTORE_LOCK_’
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’

The method is disabled by ‘vSphere Data Protection’

This method is disabled by ‘moref=vm-ID’

Error:fault.MethodDisabled.summary

Storage vMotion fails with the generic error message:

The method is disabled by XXXXXXXXXXX

When you start vMotion, you see a pop-up message similar to:

Invalid / explicitly disabled state operation is invoked

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