mgenet
2 Posts
Quote from mgenet on November 13, 2019, 10:46 pm
Hello
We am running PetaSAN version 2.3.0 on 5 HP hardware chassis with Hyper-V as the hypervisor. We have an issue with live migration and Microsoft need us to shutdown all node and start three of them and then they will do some testing, unsure how long this will be.
Questions are:
- will this trigger a rebuild/remap of the data on those three live servers as the other two nodes are down for more than 10 minutes?
- if it does (which is something we don't want to happen as the two nodes down will be brought back online, in a few hours)., is there a means to delay/stop the trigger until the other two nodes are online?
Thank you
--Mark
Hello
We am running PetaSAN version 2.3.0 on 5 HP hardware chassis with Hyper-V as the hypervisor. We have an issue with live migration and Microsoft need us to shutdown all node and start three of them and then they will do some testing, unsure how long this will be.
Questions are:
- will this trigger a rebuild/remap of the data on those three live servers as the other two nodes are down for more than 10 minutes?
- if it does (which is something we don't want to happen as the two nodes down will be brought back online, in a few hours)., is there a means to delay/stop the trigger until the other two nodes are online?
Thank you
--Mark
admin
2,930 Posts
Quote from admin on November 14, 2019, 9:16 am
you can put the cluster in maintenance from ui and set noout,nobackfill,norecover,norebalance
you can put the cluster in maintenance from ui and set noout,nobackfill,norecover,norebalance
