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 migration fails with the error: The method is disabled by 'SYMC-INCR dd-mm-yyyy hh:mm' (2008957)

Symptoms

  • Storage vMotion migration fails.
  • In vCenter Server 5.0, the Migrate option is unavailable.
  • You cannot drag and drop a virtual machine from one folder to another.
  • You are unable to move virtual machines between folders.
  • You cannot move virtual machine between folders.
  • The virtual machine Remove from Inventory option is unavailable.
  • 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

Cause

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

Resolution

This is a known issue affecting VMware vCenter Server. Currently, there is no resolution.

To work around this issue, perform one of these options:
  • Schedule another backup.
  • Remove and re-add the virtual machine from the inventory.
  • Remove and re-add the ESXi/ESX hosting the virtual machine from the inventory.
  • Manually remove entries from the vCenter Server database.
Caution: Take a full backup of your existing database before proceeding with any of these options. Involve a Database Administrator if you have any difficulty with these steps.

Schedule another backup

Schedule another backup of the affected virtual machine. If this completes successfully, the entries should be removed from the vCenter Server database and this allows a Storage vMotion of the virtual machine.

Remove and re-add the virtual machine from the inventory

To remove and re-add the virtual machine from the inventory:
  1. Power off the virtual machine.
  2. In 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.

    Note
    : This gives the virtual machine a new ID.

  5. Power on the virtual machine and retry the Storage vMotion.

Remove and re-add the ESX/ESXi from the inventory

  1. In the vSphere Client, right-click the ESXi/ESX host and click Disconnect.
  2. Right-click the disconnected ESXi/ESX host and click Remove from inventory.
  3. After the host is removed from inventory, right-click the cluster and click Add Host.
  4. Provide the IP address or hostname of the ESXi/ESX host and the root username and password.

Manually remove entries from the vCenter Server database

To manually remove the entries from the vCenter Server database:

Caution: Take a full backup of your existing database before proceeding with this workaround. Involve a Database Administrator if you have any difficulty with 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%'

    where Virtual-Machine-Name is the name of the virtual machine. Leave the percentage (%) signs flanking the name.

  4. Take note of the vm-ID_Number value returned by the SQL statement in step 3, as this will be required in the SQL statement in steps 5 and 6.
  5. To confirm the stale entry, run this command against the vCenter Server database:

    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 VMware VirtualCenter Server services, then retry the Storage vMotion. For more information, see Stopping, starting, or restarting vCenter services (1003895).

Manually remove entries from the vCenter Server Appliance vPostgres database

To manually remove the entries from the vCenter Server Appliance vPostgres database for vCenter Server Appliance 5.0 Update 1, 5.1.x and 5.5.x:

Caution: Take a snapshot and/or full backup of your existing database before proceeding with this workaround. For guidance on backing up the vPostgres database for the vCenter Server Appliance, see Backing up and restoring the vCenter Server Appliance vPostgres database (2034505). Involve a Database Administrator if you have any difficulty with these steps.
  1. Connect to the vCenter Server Appliance via SSH. For more information, see Enable or Disable SSH Administrator Login on the VMware vCenter Server Appliance section in the vCenter Server and Host Management Guide.
  2. Stop the VMware VirtualCenter Server service using this command:

    service vmware-vpxd stop

  3. Take a backup of the vCenter Server database. For more information, see Backing up and restoring the vCenter Server Appliance vPostgres database (2034505).
  4. Run this command against the vCenter Server database.

    sudo /opt/vmware/vpostgres/1.0/bin/psql -d VCDB vc -c "select * from VPX_VM WHERE FILE_NAME LIKE '%Virtual-Machine-Name%';"

    where Virtual-Machine-Name is the name of the virtual machine. Leave the percentage (%) signs flanking the name.

  5. Take note of the numerical ID value returned by the SQL statement in step 4, as this will be required in the SQL statement in steps 6 and 7.
  6. To confirm the stale entry, run this command against the vCenter Server database:

    sudo /opt/vmware/vpostgres/1.0/bin/psql -d VCDB vc -c "select * from VPX_DISABLED_METHODS WHERE ENTITY_MO_ID_VAL = 'vm-ID from step 4';"

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

    sudo /opt/vmware/vpostgres/1.0/bin/psql -d VCDB vc -c "delete from VPX_DISABLED_METHODS WHERE ENTITY_MO_ID_VAL = 'vm-ID from step 4';"

  8. Start vCenter Server service, then retry the Storage vMotion. For more information, see Stopping, starting, or restarting vCenter Server Appliance services (2054085).
 
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.

Impact/Risks

Take a full backup of your existing database before proceeding with any of the workarounds in this article. Involve a Database Administrator if you have any difficulty.

Removing a virtual machine from inventory results in the loss of historical performance data. Removing an ESXi/ESX host from the inventory results in the loss of the historical performance data from both the host and all virtual machines registered with that host. If you are removing the host from inventory, migrate all virtual machines except the affected one from the host, so that the other virtual machines are unaffected.

Additional Information

Tags

storage-vmotion-fails

See Also

This Article Replaces

2009929

Update History

02/24/2012 - Added a symptom that the Migrate option is grayed out 05/20/2013 - Added symptom, This method is disabled by 'moref=vm-<ID>' 01/14/2014 - Added SQL query to confidential section.

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

  • 60 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)
  • 60 Ratings
Actions
KB: