Software-based VM-centric and flash-friendly VM storage + free version
Moderators: anton (staff), art (staff), Max (staff), Anatoly (staff)
-
yaroslav (staff)
- Staff
- Posts: 3424
- Joined: Mon Nov 18, 2019 11:11 am
Thu Sep 19, 2024 4:13 pm
Got it.
Please remove write-back caching if you use it.
Could you please share the screenshot from the Windows-based management console?
If both nodes say NOT SYNCHRONIZED and PARTNER NOT SYNCHRONIZED
1. Stop StarWindService on both
2. For one go to the headers directory and edit HA.swdsk
see the area that looks like
<node id="1" name="HAImage" shut="false" active="true" flags="0">
<storages>
<storage_ref id="1"/>
</storages>
<parameters>
<type>1</type>
<priority>2</priority>
<auto_sync>true</auto_sync>
<sync_status>1</sync_status>
<sync_delay>50</sync_delay>
<sync_traffic_share>50</sync_traffic_share>
<failover_conf>0</failover_conf>
<last_sync_snap_id>0</last_sync_snap_id>
<alua_access_state>0</alua_access_state>
</parameters>
</node>
<node id="2" name="iqn.2008-08.com.starwindsoftware:10.1.101.4-swstorage3" shut="false" active="true">
<storages>
<storage_ref id="2"/>
</storages>
<parameters>
<type>1</type>
<priority>1</priority>
<sync_status>0</sync_status>
<alua_access_state>0</alua_access_state>
<type_bitmap>RAM</type_bitmap>
</parameters>
</node>
</header>
3. Start the service.
4. Bring up the storage in Failvoer Cluster or rescan ESXi hosts.
5. Make sure data is up-to-date.
6. If up-to-date, start StarWind Service on the remaining node.
-
yaroslav (staff)
- Staff
- Posts: 3424
- Joined: Mon Nov 18, 2019 11:11 am
Fri Sep 20, 2024 2:08 pm
Try the following
1. Stop StarWindService on both nodes.
2. Edit the HA.swdsk and HA.swdsk.bak for one node.
3. Start StarWindService for that node.
Do you see iSCSI connections to be connected in iSCSI Initiator for that node?