I know that hardware specs will have a large influence on the answer to my question but I am trying to get a general idea of best practices. For reference, I am running three nodes on Dell servers each server having three RAID 0, 1.2TB SAS 15k drives, dual 10 gig links for sync and iSCSI channels an...

I have a similar issue that I think is related to yours and I'm also running a 3 node setup. I have set the iSCSI initiator MPIO device details to be failover only and pointing to the local adapter 127.0.0.1 as the target portal and active as per Starwind's instructions. When the server gets reboote...

Thanks for the link, it worked fine. I may try to do the upgrade this weekend after hours as I want to backup the VMs just in case something happens to the cluster. Does this latest build 7509 solve the issues in the previous version of the growing lsfsx duplicate files in a thin provisioned device?...

For the life of me I can not figure out how to download the latest version to update our existing installation. I have followed the FAQ which says to login which I've done and I only get the option to download the free or trial version. We have purchased the full version of the product. The other pa...

So it looks like my issue with the iSCSI targets was caused by another issue that I had opened with Starwind support. Anatoly confirmed that a bug exists if you manually edit the Replication node interfaces to add additional sync channels that it would disappear after a reboot. After manually modify...

I made all these changes, then rebooted each server and I'm making the changes with admin rights. For a test, I modified the cfg file on Friday night, checked that the changes were made on each server, restarted the services on each server, checked the cfg file again after restarting, and then left ...

Can you doublecheck if the string below in the starwind.cfg file is uncommented on both servers? <!-- <iScsiDiscoveryListInterfaces value="1"/>--> Yes it is uncommented on all servers. That's one of the first things I had to do when initially setting it up. However, I just upgraded to the...

You are crossing traffic so two separate sync channels and iscsi... hum I dunno I think I'd like to hear Starwind chime in. I would think you would not want to mix traffic or what that would cause (caveats) ? but yes you are right since you have two sync and iscsi and one goes down in that configur...

You have to have MPIO turn on. " Just trying to understand what your 10Gbe Intel iSCSI is for when you said that your have two 1Gbe ports on each server for iSCSI to the Synology." did you look at my diagram and few posts back? I suppose you could call it over kill but I wanted all of my ...

I don't know if this helps you, but I have almost the exact same server 3 Node setup that Anatoly from Starwind helped setup just last week and I am using direct connect. I have two Dual 10GBe Nic's (4 total per server) also two 300GB 10k sas as a RAID 0 for the OS and siz 900BGGB sas in Raid 0 for...

This is driving me nuts so I'm hoping that someone here may have encountered this. I have a three node setup and the Starwind clusters are replicating perfectly between all three with no issues. The problem is trying to connect the iSCSI targets with MPIO between two of the servers. I have 4 10Gig p...

That is exactly the design diagram I was looking for as an reference over a month ago on how to setup our system! If I had that at the start, I wouldn't have had to try out so many different iterations of network design. In your case, do you have eight network ports in each server? I was thinking of...

We are using FO because that is what you guys have stated in your manuals. That link you provided shows exactly that on page 24.

I will be setting up three CSVs as recommended by your engineer, two 200GB ones and one 1.6TB one, each one hosted by a different primary server. I'm estimating each CSV to only need to handle about 1000-1500 IOPS at extreme peak times with about 300-600 IOPS during normal times. Do you think this i...

I've got a Microsoft 2012 R2 cluster setup in a 3-node HA configuration with a 1GB witness disk which has been assigned for the quorum. In the witness disk properties, I have confirmed that all three of my servers are possible owners but if the owner node of the witness goes offline, it does not aut...