Hey all, any input would be greatly appreciated. I'm testing Starwind for the first time. I've installed Starwind on Server 2008. I'm running a machine with 2003 R2 and the Window ISCSI initiator. When I create an "Advanced Virtual" target with "Snapshot and CDP" selected, I cannot connect to it. The initiator hangs, the disk manager will freeze indefinitely and eventually the machine will freeze.
The same thing happens if I attempt to use Starport instead of Microsoft's initator. I can get everything to work with a basic image, just not Snapshot/CDP. The event log is filled with "IBV device IBV1: journal switching completed. New journal file is xxxxxxxx" and the server log has a few of these over and over:
7/26 12:36:57.546 b28 T[38d,1]: session 0x38d, connection 0x38d : end of stage 1, next stage 3.
7/26 12:36:57.546 b28 C[38d], IN_LOGIN: Event - LOGIN_ACCEPT.
7/26 12:36:57.546 b28 C[38d], LIN: T5.
7/26 12:36:58.562 bdc C[38d], LIN: recvData returned 10060
7/26 12:36:58.562 bdc C[38d], LIN: *** 'recv' thread: recv failed 10058.
7/26 12:36:58.562 b28 IBV: IBVolume_SwitchJournalFiles: >> Dev 00000000030CCAA0 'test3.ibv': Start switching of the journal 00000002.
Any thoughts? I'm probably missing something simple here.
The Latest Gartner® Magic Quadrant™Hyperconverged Infrastructure Software
