Do you have any data that is FTT=0 or just with local protection (e.g. PFTT=0,SFTT=1)? If you do and these need to remain accessible during the maintenance then I would advise moving these first (change the site in the Storage Policy and reapply it).
Other than that, your plan looks fine - use Ensure Accessibility option, No Action is used more for activities such as physically moving a whole cluster or incoming power outage (and all the data should ideally be cold).
Thanks Bob for your answer.
We do not have any data that is FTT=0 or just with local protection.
1 person found this helpful
we did not disable HA and DRS but instead created a host group "maint-hosts" and vm group "ALL VMs"
then activated a rule so that ALL VMs must not run on maint-hosts.
now let DRS do its job, and then it is much easier (faster) to bring the vsan "main-hosts" into maintenance mode with "ensure accessiblity"
when you make them exit maintenance mode again, do so quickly one after another, so that no re-placement of components would start (you raised the delay timer anyway...)
only disable or delete the "maint-rule" after you are sure there is no more data resync going on