The Latest Gartner® Magic Quadrant™Hyperconverged Infrastructure Software
Moderators: anton (staff), art (staff), Max (staff), Anatoly (staff)
I just tried this shortcut method -- yes, over 3 years later -- because a working drive was showing poor health status, and... well, it didn't work.yaroslav (staff) wrote:The procedure you shared can be performed without the downtime (i.e., Maintenance mode). You can have the production running while the other serer undergoes the maintenance as you do not need to turn off the other server.
1. Make sure to have a backup. Copy StarWind.cfg too from C:\Program Files\StarWind Software\StarWind just in case.
2. In the StarWind Management Console, check that all StarWind HA devices have the “Synchronized” status on all servers;
3. Move all Cluster resources and non-clustered VMs from the server (you can just shut down non-clustered VMs too), which is going to undergo maintenance (pause and drain the roles in the cluster);
4. Disable StarWind Service on the host that undergoes the maintenance;
5. Swap the disk;
6. Wait for the rebuild to finish.
7. Set StarWind Service to Autostart and start it again;
8. Let sync go.
Restarting StarWind VSAN only on the affected server should be sufficient.I had to stop/kill the VSAN service on both hosts to get it to restart synchronization.
You could have just recreated the mirror to that drive and waited for full synchronization to completeIf the drive had flat failed, I wonder if I could have gotten away with cloning or even just copying the drive from the other host...
I tried that first.yaroslav (staff) wrote:Thanks for your update.Restarting StarWind VSAN only on the affected server should be sufficient.I had to stop/kill the VSAN service on both hosts to get it to restart synchronization.
Ah. Not sure how to do that with PowerShell, and don't need to now. But thanks so much for your help!You could have just recreated the mirror to that drive and waited for full synchronization to completeIf the drive had flat failed, I wonder if I could have gotten away with cloning or even just copying the drive from the other host...
The procedure is pretty much Remove Replica -> Recreate the replication partner.
Sorry, I don't remember: What's the best way to share stuff like that? Just paste it in-line as code? That would make easy to include notes...yaroslav (staff) wrote:Hi,
Yes, indeed! I guess that one will be helpful for the community.
Thanks a lot.