Bad Memory Active Replication Node

[Aaron_Denton]

My setup has two Starwind servers using version 5.6.

We recently had some memory go bad on the active node of two servers that are using mirroring.

The Hyper-V hosts are currently connected directly to the images on the passive node while we work on replacing the memory.
The NICs used for replication have been unplugged.

My question: when we get the memory replaced, should we just plug the NICs back in or should we first delete the mirrors on what used to be the active node and re-create them?

[Anatoly (staff)]

If the IPs will be the same you need to disconnect from the secondary mirror, login to host, switch active mirror, perform synchronization, connect to targets and continue working.

[Aaron_Denton]

I tried this in my lab and the result was that I lost data.

Let my explain my setup a little better and maybe there's something I'm missing.

Currenly the Starwind host is the Active Mirror. Starwind service has been disabled.

My Hyper-V servers are connected to the virtual disks (.img files) on the Passive non-host Mirror server.
Many changes have been made.

Your directions seem to say I should
1. disconnect my Hyper-V hosts from the Passive MIrror server
2. Logon to Starwind host server and start the Starwind service
3. switch Active Mirror from current server (with old images) to the Passive Mirror (with the current .img files)
4. Perform a synchronization
5. Connect Hyper-V hosts to Starwind host server (which now is NOT the active mirror)

Is that correct?

[Anatoly (staff)]

As I get we had conversation via StarWind Live Chat today, and the issue is solved, correct?