Great question.. Generally No. But watch this video on HA and go to time index 9:15 this will answer your question. Have a good one. th-cam.com/video/p5H06ND7XbM/w-d-xo.html
i have vsphere 7 cluster with DRS unsuported and doing a vm migration ends up with an error ""This action is not available for any of the selected objects at this time." appreciate your support on this
Sounds like an issue with vCenter Server thinking there is some sort of outstanding task running. First I would do a few things. 1. Try a different browser / different station to do the vMotin from - In case it is a browser issue. 2. Does this error occur if you try to vMotion others vm's and VM's on other hosts? 3. Check the health of the cpu/mem/databse on the vCenter server using the vCenter Serve Management interface (port 5480). 4. All else fails I would shutdown vCenter server and powr it back up (make sure you do a clean shutdown and don;t just power it off).. Keep us posted.
Everything we need to know about DRS is here. Thank you Steve 👌👌
My pleasure. Have a good one
Thanks for an excellent overview and demonstration.
Thanks for watching. Have a good one
Thank you Steve, Great content 👏
Very welcome Have a good one
Great work.
Thank you! Cheers!
Great content!
Thanks a lot. Have a great day
Great demonstration of DRS! Do you know if DRS would kick in if a single plug is pulled from a dual powersupply server?
Great question.. Generally No. But watch this video on HA and go to time index 9:15 this will answer your question. Have a good one.
th-cam.com/video/p5H06ND7XbM/w-d-xo.html
Thank you for the great content ❤
Thanks for watching! You have a good one
i have vsphere 7 cluster with DRS unsuported and doing a vm migration ends up with an error ""This action is not available for any of the selected objects at this time." appreciate your support on this
Sounds like an issue with vCenter Server thinking there is some sort of outstanding task running. First I would do a few things.
1. Try a different browser / different station to do the vMotin from - In case it is a browser issue.
2. Does this error occur if you try to vMotion others vm's and VM's on other hosts?
3. Check the health of the cpu/mem/databse on the vCenter server using the vCenter Serve Management interface (port 5480).
4. All else fails I would shutdown vCenter server and powr it back up (make sure you do a clean shutdown and don;t just power it off)..
Keep us posted.