(DP) Support Tip: Could not lock vMotion

0 Likes
6 months ago

Error Message
A warning message regarding vMotion is logged during backup .


[Normal] From: VEPALIB_VMWARE@hostname "Barlist" Time: DD/MM/YYYY HH:MM:SS
Virtual Machine 'VM Name': Locking vMotion ...

[Warning] From: VEPALIB_VMWARE@hostname "Barlist" Time: DD/MM/YYYY HH:MM:SS
Virtual Machine 'VM Name': Could not lock vMotion.


Cause
There is a potential risk that the VM was not backed up correctly .

According to debugs, the user was not allowed to lock vMotion .


[110] [VddkUtil::diskLibLog] VixDiskLibVim: Error 3014 (listener error VmodlVimFaultNoPermission).
[110] [VddkUtil::diskLibLog] VixDiskLibVim: Disable vMotion methods failed with VmodlVimFaultNoPermission at 1808.

[110] [VddkUtil::diskLibLog] VixDiskLib: VixDiskLib_PrepareForAccess: Disable Storage VMotion failed. Error 3014 (Insufficient permissions in the host operating system) (fault NoPermission, type VmodlVimFaultNoPermission, reason: (none given), translated to 3014) at 4724.


The error indicates the user doesn't have the following privileges .

Global -> Disable methods
Global -> Enable methods
Global -> Licenses

Workaround / Fix
If the user actually has the privileges, there might be some unexpected issues regarding the privileges with the user .
Please consider to recreate the user with right privileges, or try to use another user that has the privileges .
Regarding the required privileges, please refer to a documentation .

Ref.) https://docs.microfocus.com/itom/Data_Protector:2020.08/VMwareConfigureIntegration

Labels:

Support Tip
Comment List
Anonymous
Related Discussions
Recommended