This post is also available in: Italian

Reading Time: < 1 minute

Recenltly I’ve got some issue with Storage vMotion due to the “lock” function used by some backup programs. I’ve write about it related with Symantec Backup Exec, but this time was with VMware Data Protector (VDP).

Usually, backup programs disable Storage vMotion during the backup process to avoid datastore changes (and issue during the copy, considering that starting from vSphere 5.0 it’s possible use Storage vMotion also on VM with snapshots). But if the backup process fail, some backup programs does not clear this information correctly.

A solution could be schedule another backup to fix it. Another is clear the vCenter database.

The KB 2008957 (Storage vMotion fails with the error: The method is disabled by ‘SYMC-INCR dd-mm-yyyy hh:mm’) also suggest to power-off the VM and re-add to inventory, but this does not always works.


Virtualization, Cloud and Storage Architect. Tech Field delegate. VMUG IT Co-Founder and board member. VMware VMTN Moderator and vExpert 2010-24. Dell TechCenter Rockstar 2014-15. Microsoft MVP 2014-16. Veeam Vanguard 2015-23. Nutanix NTC 2014-20. Several certifications including: VCDX-DCV, VCP-DCV/DT/Cloud, VCAP-DCA/DCD/CIA/CID/DTA/DTD, MCSA, MCSE, MCITP, CCA, NPP.