Software-based VM-centric and flash-friendly VM storage + free version
Moderators: anton (staff), art (staff), Max (staff), Anatoly (staff)
-
EinsteinTaylor
- Posts: 22
- Joined: Thu Aug 30, 2012 12:28 am
Thu Sep 27, 2012 8:22 pm
We are considering purchasing the license to add a 3rd node to our HA environment next year but the question I have is how replication works for the 3rd node. Currently the design thoughts are to install the 3rd node locally and let everything sync, and then overnight the server to the offsite location where we will host the 3rd node and let it replicate when it comes up. The question I have is when the 3rd node is detected out of sync, does it just replicate the changes, or is it a "full sync" like what happens when one of 2 HA nodes gets out of sync?
This has significant implications for bandwidth and could affect our decision making.
-
anton (staff)
- Site Admin
- Posts: 4021
- Joined: Fri Jun 18, 2004 12:03 am
- Location: British Virgin Islands
-
Contact:
Fri Sep 28, 2012 6:50 am
It does replicate the changes. But in your case (assuming constant node downs) I think it's more convenient to use not "3 synchronous" but rather "2 synchronous + 1 asynchronous" design.
EinsteinTaylor wrote:We are considering purchasing the license to add a 3rd node to our HA environment next year but the question I have is how replication works for the 3rd node. Currently the design thoughts are to install the 3rd node locally and let everything sync, and then overnight the server to the offsite location where we will host the 3rd node and let it replicate when it comes up. The question I have is when the 3rd node is detected out of sync, does it just replicate the changes, or is it a "full sync" like what happens when one of 2 HA nodes gets out of sync?
This has significant implications for bandwidth and could affect our decision making.
Regards,
Anton Kolomyeytsev
Chief Technology Officer & Chief Architect, StarWind Software
