Hi All,
Thank you for your inputs. Much appreciated. I've managed to get this to work by doing the following:
1. Put the host into maintenance mode, select "Ensure Data accessibility...." instead of the "Full Evacuate Data"
2. Once in maintenance mode, I then go to the VSAN disk groups and delete the Disk Group for the host I am working on.
3. After waiting for VSAN to do its bit, the cluster is now running in non-compliance mode (my VMs are still running and working but non-compliant).
4. I then exit maintenance mode on the host, then put it in maintenance mode again this time selecting "Full Evacuate Data"
5. Move the host out of the cluster and remove from inventory.
I was able to rebuild the host from scratch and add back to the VSAN cluster...During this time, we knew the risk of the vsan cluster running from 1 node (+ witness) but that is fine in our case.
I don't know why it couldn't do all of the above automatically when selecting "Full Evacuate Data" the first time though...
Thank you.