Reinstall Windows - restore HA config

[lohelle]

Is it possible to backup the Starwind configuration and reinstall Windows + import settings after?

I have a secondary node in a HA pair that I need to reinstall (disk corruption on OS disk). It would be nice to be able to reinstall Windows on a new disk and just import the Starwind setup. Recreating all HA LUN's will take a few days of SVmotion...

Is this possible?

[Max (staff)]

Hello Lohelle,
You just need to back up the starwind.cfg file and make sure that all the drive letters remain the same after OS reinstall.
Good luck!
♠

[lohelle]

Perfect!
Thanks!

[anton (staff)]

Please keep us updated about your migration / backup & restore process. Thank you!

[lohelle]

The migrating went just fine btw.

In a few days I will replace my two gigabit sync channels with a single 10GBE crossover link. The two links have ip-address 10.199.198.1 (and .2 on partner) and 10.199.199.1 (and .2 on partner).

If I install the 10GBE cards on one server at the time, then change the ip-addresses (move from the 1GBE to the single 10GBE), will this work without taking starwind down? I cannot find any pointers to the sync-links in the config file. Is it configured for the ip-address or the network card?

[Anatoly (staff)]

I think the best procedure is next:
1.Turn off server1, swap NICs
2.Turn on server1, configure IP on new NIC it to the same as previous one
3.Try to initiate FastSync, if it will not start initiate FullSync
4.After synchronization process will be finished turn off server2
5.Swap NICs
6.Turn on server1, configure IP on new NIC it to the same as previous one
7.Try to initiate FastSync, if it will not start initiate FullSync


In this you shouldnt get any downtime at all.

If you have possibility to stop your production for a while you may do next:
1.Turn off server2
2.Turn off server1
3.Swap NICs on them
4.Turn on server1
5.Configure IP on new NIC
6Turn on server2
7.Configure IP on new NIC
8.Initiate FullSync (in this case server1 should be the source of data, other words you need to initiate it from server2 host in SW management console as it is shown on the picture below)

[lohelle]

I think the problem with the upper scenario is that I cannot connect the nics from 10GBE (CX4) to the existing 1Gig on the second server.
But what if I shut down server 2 (or 1), use one of my other 1Gig links (not crossover, but using production Cisco switches) where I add the sync IP, then change the sync IP on the other servers nic (same vlan).

Now, will Starwind HA "survive" moving ip's for the sync channel to an other nic "live"? I can of course stop one of the nodes so that the sync will not be active.

When both nodes are in sync using the temporary sync nic (with old IP's) I can shut down the first node, swap nic, start up again, sync, shut down node 2, swap nics, change IP's (move to 10Gig nics on both nodes) and sync?

[Anatoly (staff)]

I think the problem with the upper scenario is that I cannot connect the nics from 10GBE (CX4) to the existing 1Gig on the second server.
But what if I shut down server 2 (or 1), use one of my other 1Gig links (not crossover, but using production Cisco switches) where I add the sync IP, then change the sync IP on the other servers nic (same vlan).

Now, will Starwind HA "survive" moving ip's for the sync channel to an other nic "live"? I can of course stop one of the nodes so that the sync will not be active.

When both nodes are in sync using the temporary sync nic (with old IP's) I can shut down the first node, swap nic, start up again, sync, shut down node 2, swap nics, change IP's (move to 10Gig nics on both nodes) and sync?

Well actually they'll be connected: after you'll change IPs on the new NIC and restart starwind service SyncChannel will be online again.
Update about your plan you`ll receive tomorrow - I`ll doublecheck with our R&D.

[lohelle]

Thank you!
What I am afraid of is that BOTH nodes need to be restarted to restore the sync channel. Then I will need to shut down the entire vSphere environment.
I hope sync will be restored just by changing the IP's and wait a few seconds..

[Anatoly (staff)]

OK, little update to the best plan:
1.Turn off server1, disconnect it from all networks, swap NICs
2.Turn on server1, configure IP on new NIC it to the same as previous one, connect server1 to all the networks
3.Synchronization should start automatically
4.After synchronization process will be finished turn off server2
5.disconnect server2 from all networks, swap NICs
6.Turn on server2, configure IP on new NIC it to the same as previous one
7.Connect server2 to all the network, synchronization should start automatically

In case of your plan:

But what if I shut down server 2 (or 1), use one of my other 1Gig links (not crossover, but using production Cisco switches) where I add the sync IP, then change the sync IP on the other servers nic (same vlan).

You will still have to start sync manually.

[dmjoker]

Dear collegues,
I have reinstalled Windows on node 2. Before reinstalling it, I copied starwind.cfg file.

On newly installed Windows I installed Starwind, putted starwind.cfg on starwind folder and restarted service. On management console appeared targets, but starting full synchronization I took the following error:

Synchronization cannot be started. Waiting for connection from partner

Failed: operation cannot be compledet

What did I do wrong? =)

[Constantin (staff)]

Basically this error means that connection over sync interface can`t be established. Plz double check if you use the same IP addresses as previously.

[dmjoker]

Check adresses - all match. Error continues to appear

[Constantin (staff)]

Check in console iSCSI Sessions tab. There should be 4 sessions. If not - try disable firewall on both nodes and restart service

[dmjoker]

On working node (node 1) in console one session (from working node).
On broking node (with reinstalled Windows, node 2) no sessions.
Firewall disabled, TCP, UDP and ICMP traffic pass (tested twice).

On broken node i see very short list of properties - maybe this can help?