Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Storage vMotion fails with the error: The method is disabled by 'SYMC-INCR dd-mm-yyyy hh:mm' (2008957)

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_'
      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'
      E      rror Stack
      Call "VirtualMachine.Relocate" for object "VM-NAME" on vCenter Server "vCenter-Name" failed

    • The method is disabled by 'Data Recovery'

  • Storage vMotion fails with generic error message:

    The method is disabled by XXXXXXXXXXX

  • 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

VMware is aware of this issue.

There are several workarounds which can resolve this issue. See the following.

(1) To workaround this issue:

Schedule another backup of the affected VM. If this completes successfully, the entries should be removed from the vCenter Server database and will allow the VM to be SVmotioned.

(2) To workaround this issue:

Note: VMware strongly recommends you back-up your existing database before proceeding with this KB. Involve a Database Administrator if you find any difficulty in these steps.
  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.

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

Note: VMware strongly recommends you back-up your existing database before proceeding with this KB. Involve a Database Administrator if you find any difficulty in these steps.
  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.
For more information, see Manually enable vSphere solutions 1021265.
 
THE CONTENT OF THIS ARTICLE IS PROVIDED "AS-IS," AND TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, VMWARE DISCLAIMS ALL OTHER REPRESENTATIONS AND WARRANTIES, EXPRESS OR IMPLIED, REGARDING THIS CONTENT, INCLUDING THEIR FITNESS FOR A PARTICULAR PURPOSE, THEIR MERCHANTABILITY, OR THEIR NONINFRINGEMENT. VMWARE SHALL NOT BE LIABLE FOR ANY DAMAGES ARISING OUT OF OR IN CONNECTION WITH THE USE OF THIS CONTENT, INCLUDING DIRECT, INDIRECT, CONSEQUENTIAL DAMAGES, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF VMWARE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Tags

storage-vmotion-fails

This Article Replaces

2009929

Update History

02/24/2012 - Added a symptom that the Migrate option is grayed out

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 41 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 41 Ratings
Actions
KB: