Sun Nov 14, 2021 12:30 pm
Yaroslav, thank you for your answer.
I understand that each replica can present storage.
This is HyperV based Windows Server VM replicating virtual disk to another HyperV based Windows Server VM scenario/configuration - does not include clustering.
So lets assume two nodes with corresponding replicating devices.
Fail is situation where one computing node (VM) is destroyed, and can not be recovered.
Let suppose thats priority "First" node that failed. We use the alive node replica now, without data loss. Then the failing node is rebuilt from scratch, Starwind set up again on that node, and synchronization/replication must be configured towards it - it needs to have lower priority. How would we do that?
Or maybe the "priority first" node did not fail in way it cannot be recovered again, it just can not be started for the time being, so we must consume virtual disk on another node.
Then, when failing node starts up again it needs to have lower priority since we had changed on another node already.
