The replication should be configured using Synchronous “Two-Way” Replication mode:
Synchronous or active-active replication ensures real-time synchronization and load balancing of data between two or three cluster nodes. Such a configuration tolerates the failure of two out of three storage nodes and enables the creation of an effective business continuity plan. With synchronous mirroring, each write operation requires control confirmation from both storage nodes. It guarantees the reliability of data transfers but is demanding in bandwidth since mirroring will not work on high-latency networks.
1. Right-click on the DS1 device and select Replication Manager from the shortcut menu.
2. Select the Add Replica button in the top menu.
3. Select Synchronous “Two-Way” replication as a replication mode.
4. Specify a partner Host name or IP address and Port Number.
5. Select Failover Strategy.
6. Select Create new Partner Device and click Next.
7. Select a partner device Location and click Next.
8. Select Synchronization Journal Strategy and click Next.
NOTE: There are several options – RAM-based journal (default) and Disk-based journal with failure and continuous strategy, that allow to avoid full synchronization cases.
RAM-based (default) synchronization journal is placed in RAM. Synchronization with RAM journal provides good I/O performance in any scenario. Full synchronization could occur in the cases described in this KB: Reasons why Full Synchronization may start – StarWind Knowledge Base
Disk-based journal placed on a separate disk from StarWind devices. It allows to avoid full synchronization for the devices where it’s configured even when StarWind service is being stopped on all nodes.
Disk-based synchronization journal should be placed on a separate, preferably faster disk from StarWind devices. SSDs and NVMe disks are recommended as the device performance is defined by the disk speed, where the journal is located. For example, it can be placed on the OS boot volume.
It is required to allocate 2 MB of disk space for the synchronization journal per 1 TB of HA device size with a disk-based journal configured and 2-way replication and 4MB per 1 TB of HA device size for 3-way replication.
Failure journal – provides good I/O performance, as a RAM-based journal, while all device nodes are in a healthy synchronized state. If a device on one node went into a not synchronized state, the disk-based journal activates and a performance drop could occur as the device performance is defined by the disk speed, where the journal is located. Fast synchronization is not guaranteed in all cases. For example, if a simultaneous hard reset of all nodes occurs, full synchronization will occur.
Continuous journal – guarantees fast synchronization and data consistency in all cases. Although, this strategy has the worst I/O performance, because of frequent write operations to the journal, located on the disk, where the journal is located.
9. Click Change Network Settings.
10. Specify the interfaces for Synchronization and Heartbeat Channels. Click OK and then click Next.
172.16.20.* -Synchronization
172.16.10.* and Management as HeartBeat
11. In Select Partner Device Initialization Mode, select Synchronize from existing Device and click Next.
12. Click Create Replica.
13. Click Close to close the wizard.
14. The successfully added device appears in StarWind Management Console.
15. Right-click on the DS2 device and select Replication Manager from the shortcut menu.
16. Select the Add Replica button in the top menu.
17. Select Synchronous “Two-Way” replication as a replication mode.
18. Specify a partner Host name or IP address and Port Number.
19. Select Failover Strategy.
20. Select Create new Partner Device and click Next.
21. Select a partner device Location and click Next.
22. Select Synchronization Journal Strategy and click Next.
NOTE: There are several options – RAM-based journal (default) and Disk-based journal with failure and continuous strategy, that allow to avoid full synchronization cases.
RAM-based (default) synchronization journal is placed in RAM. Synchronization with RAM journal provides good I/O performance in any scenario. Full synchronization could occur in the cases described in this KB: Reasons why Full Synchronization may start – StarWind Knowledge Base
Disk-based journal placed on a separate disk from StarWind devices. It allows to avoid full synchronization for the devices where it’s configured even when StarWind service is being stopped on all nodes.
Disk-based synchronization journal should be placed on a separate, preferably faster disk from StarWind devices. SSDs and NVMe disks are recommended as the device performance is defined by the disk speed, where the journal is located. For example, it can be placed on the OS boot volume.
It is required to allocate 2 MB of disk space for the synchronization journal per 1 TB of HA device size with a disk-based journal configured and 2-way replication and 4MB per 1 TB of HA device size for 3-way replication.
Failure journal – provides good I/O performance, as a RAM-based journal, while all device nodes are in a healthy synchronized state. If a device on one node went into a not synchronized state, the disk-based journal activates and a performance drop could occur as the device performance is defined by the disk speed, where the journal is located. Fast synchronization is not guaranteed in all cases. For example, if a simultaneous hard reset of all nodes occurs, full synchronization will occur.
Continuous journal – guarantees fast synchronization and data consistency in all cases. Although, this strategy has the worst I/O performance, because of frequent write operations to the journal, located on the disk, where the journal is located.
23. Click Change Network Settings.
24. Specify the interfaces for Synchronization and Heartbeat Channels. Click OK and then click Next.
172.16.20.* -Synchronization
172.16.10.* and Management as HeartBeat
25. In Select Partner Device Initialization Mode, select Synchronize from existing Device and click Next.
26. Click Create Replica.
27. Click Close to close the wizard.
28. The successfully added device appears in StarWind Management Console.
Extend StarWind devices:
1. Right-click on the DS1 device and select (Extending Size of HA (High Availability Device) from the shortcut menu.
2. Enter the Amout of space to extend.
DS1 need to add 511GB
DS2 need to add 1023GB