We're suddenly stuck with our VCSA (7.02) on a host. When trying to mirate the VCSA (either manually or automatically) from one host to another, the process just fails with "Failed to receive migration. The source detected that the destination failed to resume."
We had this last week with 3-4 VMs, but this could be resolved by shutting down and migrate those (not-so-important) VMs offline. After powering on on a different host, the "live" migration worked fine again with those VMs.
But this is not feasible with the VCSA itself...
a) Any ideas what may cause this? We're running a small VSAN cluster, there are some capacity warnings (at 83%) but no real errors.
b) Which log files might give a bit more insight here? I couldn't really find anything conclusive so far... do I need to check the VCSA or ESX logs for migration problems?
So far we had a 2,5h VMWare session... tried a lot but failed. More logs uploaded... postponed to Monday.
We'll see... was asked to reboot the host the VCSA was residing on but had to decline... too much going on right now for something like that out of the blue.
A lot of troubleshooting was done to no conclusion, even the network team got involved.
In the meantime we added a secondary storage (Synology iSCSI target) to our small cluster and tried to “storage move” the stuck VCSA (on Host3 and VSAN storage) to the Synology.
This worked well, the VCSA transferred with no errors to the Synology target.
-After this storage move, the VCSA was migrate-able AGAIN from Host3 to the other two hosts…
-Another VCSA storage move back to the VSAN, still movable between hosts 1-3
There was NO conclusion WHY this lock had happened. We're still a bit worried what went wrong but this might help others if they experience the same problem.