03-06-2012 05:07 AM
Hi!
Do you know if the VMware backup problem "the methods from VPX_DISABLED_METHODS are not removed after a virtual machine backup task completes." is solved in the SP2 or there is (or gonna be) a patch to fix that?
This problems doesnt let you use storage vmotion after a backup was succesful.
Thanks
Mariano
Solved! Go to Solution.
03-07-2012 09:33 AM
Thanks for the anwsers, but the TECH180325 didnt say anything about storage vmotion and the VMware KB doesnt say if this problem is caused by BE o vSphere.
Right now im using the workaround proposed by Vmware in the KB, but its not a valid option because i have to shutdown the VMs causing downtime and the re-add them to the inventory.
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.
It seems to be a problem with BE not informing the complete status of the job to vcenter.
Thanks
03-06-2012 05:14 AM
Hi Mariano,
Check the release notes on the link below:
Thanks!
03-06-2012 06:00 PM
Have you looked at - http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2008957
03-07-2012 09:33 AM
Thanks for the anwsers, but the TECH180325 didnt say anything about storage vmotion and the VMware KB doesnt say if this problem is caused by BE o vSphere.
Right now im using the workaround proposed by Vmware in the KB, but its not a valid option because i have to shutdown the VMs causing downtime and the re-add them to the inventory.
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.
It seems to be a problem with BE not informing the complete status of the job to vcenter.
Thanks