Call “VirtualMachine.Relocate” for object “VM-NAME” on vCenter Server “vCenter-Name” failed or The method is disabled by ‘_DP-EPA_BACKUP_RESTORE_LOCK_’

Error: Call “VirtualMachine.Relocate” for object “VM-NAME” on vCenter Server “vCenter-Name” failed or The method is disabled by ‘_DP-EPA_BACKUP_RESTORE_LOCK_’
•    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_’

This problem may occur when the backup job completes but the entry was not removed in the DB.

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’

•    A pop-up message similar to the following may occur when you start storage vMotion

Invalid / explicitly disabled state operation is invoked

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.


To workaround this issue:
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.

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

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.


useradd vs adduser differences

Today I understand some basic difference about the useradd and adduser command in linux with different distros.

Debian or Ubuntu:

In this distro, adduser is a perl script which uses useradd to perform a variety of tasks. Example is given below.

root@hostname:~# adduser test1

Adding user `test1′ …

Adding new group `test1′ (1003) …

Adding new user `test1′ (1002) with group `test1′ …

Creating home directory `/home/test1′ …

Copying files from `/etc/skel’ …

Enter new UNIX password:

Retype new UNIX password:

passwd: password updated successfully

Changing the user information for test1

Enter the new value, or press ENTER for the default

Full Name []: test1

Room Number []: 1

Work Phone []: 2

Home Phone []: 3

Other []: 4

Is the information correct? [Y/n] y


If you use useradd then it creates the user by default and returns. Example is given below.

root@hostname:~# useradd test


You can see the difference by

root@hostname:~# cat /etc/passwd |grep test




Fedora, RedHat or CentOS:

In these RedHat based systems, adduser is present as a symbolic link to the actual useradd command.

[root@hostname1 ~]# ls -l /usr/sbin/adduser

lrwxrwxrwx. 1 root root 7 Dec 16  2011 /usr/sbin/adduser -> useradd

[root@hostname1 ~]#

Storeoncesoftware store(gateway) failed to start

Error: When you try to start the store in HP Data protect storeoncesoftware (Depdupe) it fails and gets an error message “ Failed to start the store” and when you execute the command

C:\> storeoncesoftware –list_store the store status will be in stopped state.”

Root cause: This problem occurs due to bad integrity in the backup file and we need to remove those files.


The following are the solution to remove the bad integrity files and the diag files in task_hk folder.

To identify this file we need to run the gokhans collector tool, the url link is given below.

To run this js file the steps are given below.

a. Open an MS-DOS prompt
b. Run the script using the following syntax:
c.  c:\> cscript //B //Nologo sosdc_win.js >sosdc.html

After getting the html result you can identify the filepath of bad integrity file and do the procedure given below.

1.Stop all stores using command “StoreOnceSoftware –stop_store –name=StoreName”

2.Stop StoreOnceSoftware service

3. Remove s.bad_integrity file

4. Delete all the files and directories under the folder $StoreRoot/StoreOncelibrary/dvol_000000x/committed/storemgr/store.d/store_x/ (you will see one xml file)

(x is 01, if the store is the first store; 02 for the second store; and so on)

5. Start StoreOnceSoftware service with debug

On Windows using command “sc start StoreOnceSoftware –log_level=tracing”

On Linux using command “/opt/omni/lbin/StoreOnceSoftware –daemon –log_level=tracing”

6. Check if the store can be started or not using command “StoreOnceSoftware –list_stores”, check the status of the store.