I've just updated VDP to 5.1.10.32 following Administration Guide. I removed snapshot after update but I'm not able to set disks to "Independent - Persistent“ mode again. I've got "File []/vmfs/volumes/5093aae5-979ec04c-8556-180373ede2e6/vSphere Data Protection/vSphere Data Protection_2-000001.vmdk was not found“ message first and "Cannot complete operation due to concurrent modification by another operation." messages now. No change after reboot.
Could it be related to not running VMware Tools in vCenter Appliance?
There was a vCenter problem. After solving VMware Tools problem I was able to set disks back to "Independent - Persistent“ mode.
Strange to see the VM still pointing to snapshot disk(/vSphere Data Protection_2-000001.vmdk) even after snapshot deletion. Try pointing the VM to original base disk ( without -00000x.vmdk)
I'm not sure about the moment just after removing snapshot and my very first attempt to set disks but VDP VM doesn't pointing to snapshot disk now:
~ # ls -la /vmfs/volumes/storage_backup/vSphere\ Data\ Protection/
drwxr-xr-x 1 root root 3640 May 23 07:56 .
drwxr-xr-t 1 root root 3780 May 22 10:04 ..
-rw-r--r-- 1 root root 73 May 9 13:53 vSphere Data Protection-bd1fd67b.hlog
-rw------- 1 root root 4294967296 May 23 07:56 vSphere Data Protection-bd1fd67b.vswp
-rw------- 1 root root 274877906944 May 23 11:58 vSphere Data Protection-flat.vmdk
-rw------- 1 root root 8684 May 23 07:56 vSphere Data Protection.nvram
-rw------- 1 root root 535 May 23 07:56 vSphere Data Protection.vmdk
-rw-r--r-- 1 root root 43 May 22 22:49 vSphere Data Protection.vmsd
-rwxr-xr-x 1 root root 4465 May 23 08:05 vSphere Data Protection.vmx
-rw------- 1 root root 0 May 23 07:56 vSphere Data Protection.vmx.lck
-rw-r--r-- 1 root root 278 May 23 08:05 vSphere Data Protection.vmxf
-rwxr-xr-x 1 root root 4465 May 23 08:05 vSphere Data Protection.vmx~
-rw------- 1 root root 274877906944 May 23 11:58 vSphere Data Protection_1-flat.vmdk
-rw------- 1 root root 537 May 23 07:56 vSphere Data Protection_1.vmdk
-rw------- 1 root root 274877906944 May 23 11:59 vSphere Data Protection_2-flat.vmdk
-rw------- 1 root root 537 May 23 07:56 vSphere Data Protection_2.vmdk
-rw------- 1 root root 107374182400 May 23 11:59 vSphere Data Protection_3-flat.vmdk
-rw------- 1 root root 566 May 23 07:56 vSphere Data Protection_3.vmdk
-rw-r--r-- 1 root root 3561352 May 22 21:50 vmware-10.log
-rw-r--r-- 1 root root 158223 May 22 22:41 vmware-11.log
-rw-r--r-- 1 root root 151891 May 23 07:50 vmware-12.log
-rw-r--r-- 1 root root 7225456 Jan 9 21:53 vmware-7.log
-rw-r--r-- 1 root root 185477 Jan 9 22:14 vmware-8.log
-rw-r--r-- 1 root root 28654154 May 9 13:53 vmware-9.log
-rw-r--r-- 1 root root 129023 May 23 08:07 vmware.log
-rw------- 1 root root 98566144 May 23 07:56 vmx-vSphere Data Protection-3172980347-1.vswp
I was surprised with the first message because I've removed snapshot just before and no error or warning appeared.
There was a vCenter problem. After solving VMware Tools problem I was able to set disks back to "Independent - Persistent“ mode.
I just met with this issue.
Solution: With admin acount you can try to cancel your task showed in "work in progress " window (In french we called Travail en cours )
And try again! This will surely solve the problem !