VSA - HA Pair

Software-based VM-centric and flash-friendly VM storage + free version

Moderators: anton (staff), art (staff), Anatoly (staff), Max (staff)

Post Reply
Jimmy9008
Posts: 7
Joined: Thu Sep 28, 2017 8:34 am

Thu Sep 28, 2017 3:03 pm

Hey folks,

I have two servers. Server A, and Server B. Server A has Hyper-V role installed on WS2016. Server B the same.
I have created a VM using the Hyper-V VSA on server A. Same on server B.
Both have a 20 GB VHD for target and each can see its own storage device.

I have created a virtual switch on both servers for Sync and iSCSI, each mapped to a physical NIC.
The two servers are connected on their interfaces correctly.

Whenever I create a HA image, specifying the correct iSCSI network + Heartbeat and Sync network + Heartbeat, I lose access to both VSAs.
'Starwind Service not found on Host 127.0.0.1' <- for both hosts.

Any ideas here? Just playing with this, so if I'm doing it wrong no problem...

Best,
Jim
TheBoy
Posts: 8
Joined: Fri Sep 29, 2017 6:40 pm

Sun Oct 01, 2017 2:30 pm

I'm seeing similar on VSA for ESX :(
Michael (staff)
Staff
Posts: 319
Joined: Thu Jul 21, 2016 10:16 am

Tue Oct 03, 2017 3:13 pm

Hello guys,
It looks like the reason of the issue is configured L1 cache on devices and lack of RAM for VSA.
Please try to create devices without cache. It should work!
Post Reply