The issue is no tthat simple of you ever want to move hyperv instances. if you use StarWind as ONE LUN for ONE server, you can not easily move hyper-v instances. I suggest: * Use FILE servers for the vhd files of the operating systems. Do NOT use ISCSI, unless you run a file system that can deal wi...
The only reason we were thinking of using smaller images, would be in case the Starwind IMG file became corrupted somehow. If it did and we only had one large IMG file, we would lose all of our VHD files too.
This is a best practice question that I can't figure out. We are using Starwind on two 2TB servers as the SAN for our virtualised Hyper-V network. We will have two Host servers that have 32GB RAM and will host about 10 servers (File servers, print server, Exchange, forums, sharepoint etc.). Now, sho...
Thanks. I've never seen this program, but I think you've found something all right. There are loads of this kind of error: 76584 23.623262 192.168.148.1 192.168.148.11 TCP iscsi-target > 49309 [ACK] Seq=28541 Ack=83185265 Win=40960 [TCP CHECKSUM INCORRECT] Len=0 TSV=38739 TSER=35207709 Emailing the ...
I can certainly send you the logs. There are no iSCSI initiator machines set up yet though. I have not heard of wireshark before, but do you want me to try to capture network traffic between the two starwind machines?
Just crashed again. I guess having the Jumbo Frames disabled did not make a difference. I am in the middle of building a new network here and haven't been able to use the storage properly for the month that I've been here. It's embarrassing, so we are going to have to look for another product pretty...
Right, I actually replied to a member of staff on Friday, so perhaps they are not in today. I have emailled you directly vallery, so hopefully we can get to the bottom of this. As an update, I turned off "Jumbo Frames" and the servers haven't crashed again yet . My recent posts on the &quo...