What about the scenario where if we have 2-node HA and use the 'mark as synchronized' feature when one node is down -- does the remaining target switch to write-through automatically?

Graham

I second this motion!

I have a two-node hyper-v setup running v5.8 on 2008R2 as follows: NIC1, port 1: public network (100Mb to switch) for Starwind heartbeat and web traffic NIC1, port 2: unused NIC2, port 1: 192.168.10.10 (1Gb crossover) for cluster heartbeat NIC2, port 2: 192.168.20.10 (10Gb crossover) for Starwind sy...

I had this same problem. Today I upgraded one of my 2-node Hyper-v clusters and neither of the two servers had a transport key in the config file. Following the upgrade I added it in, one server at a time, and allowing fast-sync to complete. Seems to be working ok as of this writing.

Did this issue get resolved? What was the solution? I had this problem when I went from v5.6 to v5.7. I am hoping to avoid it going to v5.8.

Hi,

To fix an issue in v5.7 with 2-node Hyper-v I was advised to set iscsiPingPeriod=20 in the config file. Should I leave this in before I upgrade to v5.8, or should it be set back to 0?

Thanks...

You're not expected to do what you're doing! You cannot bring one node up and use it for production. You need to bring up BOTH nodes, run a synchronization process between them and use full serviced cluster in production after that. See it's only 50% probability (with 2 node config of course) you'l...

B/c you store new data and it's just added to database. From block device point of view there's no difference in writing set of 0xFF or 0xAA patterns to some sector - data is always considered new... We'll provide external app you'd run @ background to deal with known file systems and re-assign unu...

Hi...

Why does a dedup disk continue to grow even when I delete its contents? I created a test dedup disk at 200MB, added some files until it was full, deleted all the files, then added more files in. If I keep doing this the physical size grows beyond 200MB. Is that supposed to happen?

Thanks.

anton (staff) wrote:Please keep us updated. Thank you!

No errors after 24 hours, so looks like v5.7.1733 solved it.

So if I have a StarWind HA Setup (2 physical servers), I can only have up to two Hyper-V servers as members of a Hyper-V cluster (2 more physical servers) connect to StarWind at a time? Was not aware of that limitation. Currently running 2 Hyper-V servers in a MS cluster connected to the StarWind H...

Anatoly (staff) wrote:Update your build: the latest one is 5.7.1733. You can download it using this link.

Ok done. Now will wait 24 hours to see if the errors stop.

This is happening to me again now, except it only happens about 3 times in 24 hours and only happens on one of my machines (out of 4 total). I am on v5.7.1727 and have the iscsiPingPeriod value set to 20. This started happening after I applied Windows Updates (to all of my machines) last week. Any i...

Yes, the solution in my case was to change iscsiPingPeriod value to 20 in Starwind.cfg on the first server, restart Starwind, let sync finish, then do the same on the second Starwind server. I am only running one StarWind server? I would try the same thing on your one server then, but I'm not reall...

I'm just updated to 5.7 from 5.6 and am receiving 2 messages every minute in my logs: iScsiPrt Error Event ID 20 Connection to the target was lost. The initiator will attempt to retry the connection iScsiPrt Error Event ID 34 A connection to the target was lost, but Initiator successfully reconnect...