Hi Yaroslav,

Thanks for the insight

Regards,

Hi Yaroslav, We have 2 building side by side with separate electrical and different working hour, building A with production server (1st node) have working hour from 08:00 to 17:00 while building B (2nd node) have working hour from 09:00 to 18:00. each server must be turned off at end of working hou...

Hi Yaroslav, The full sync for 500Gb approx. took around 90 minutes, I only use 1G link for sync and heartbeat channel So the idea is to wait for 10 minutes when 1st node start, if 2nd node didn't showed up, then go to stand alone mode (either remove-hapartner or just using imagefile1 device with ta...

Hi, I've setup 2 nodes with heartbeat failover strategy using powershell script, everything is running smoothly until 2nd node (backup node) is not poweren on at the same time as 1st node (production) which cause 1st node status goes to "Not Synchronized". I know we can do "mark as sy...

Hi, yaroslav

I don't follow this bit. There's no need for manual intervention unless node1 is also restarted while node2 is down, or write-back cache is used.
>>> Yes, that's what I meant

Thanks for your help

Regards,
Hendrik Saiyan

Hi, yaroslav Thanks for the continous journal value, I also want to confirmed whether 2 Node HA with heartbeat have different behaviour with 2 Node HA with Witness node (Node Majority) ? I just test with 2 Node HA (Heartbeat), when Node1 is up and Node2 is down, the LUN still up and running until No...

Hi, yaroslav

Thanks for your help, well noted.
About continous journal, in powershell command, $bmpStrategy should be set to 1 or 2 ?

Regards,

Hendrik Saiyan

Hi yaroslav, According to your explanation : When in a node majority, you need at least 2 nodes to be up, at least one is a storage provider. Witness is not carrying any storage, so leaving it running alone will not make any impact on LUN availability My understanding that same situation apply in my...

Hi, yaroslav I've tried that, even shutdown node2, then restart node1, while keeping node3 up and running, but the LUN still failed I even download trial license key and applied for 3 nodes, then using management console to create replication partner using node majority and witness, but same problem...

Hi, I've created successfully 2 Nodes HA using Node Majority + Witness Node on Windows (install StarWind VSAN Free as application, version 8.0.19551), and I can see that device HAImage1 can synchronized. I'm using below script : param($addr="172.17.11.50", $port=3261, $user="root"...

Hi, all

I'm curious about the powershell script for remove replication partner, may I know the powershell command for remove replica partner ?

Thanks,

Hendrik

Dear Ivan,

Thanks for the info.

Regards,

Hendrik

Hi all, Recently I had tested StarWind VSAN (Free edition) to our 2 nodes Windows Server 2012 running Failover Cluster, configured as "other server" role. The cluster working as expected when both nodes are up, but in our environment, both server will be shutdown at 11 PM and started again...