Page 1 of 1

about HA, cannot resynchronize after shutdown both partners

Posted: Fri Jul 23, 2010 5:20 am
by lcqzqs
hi , after testing sw5.4 HA, there seems to be some problems after shutdown both partners.

created an HA disk on server1 and server2.
if shutdown and reboot one server, they'd be auto resynchronized. this's OK.

but if shutdown and reboot both server1 and server2, they'd both be Not Synchronized, and there''s no auto resynchronizing. By clicking 'fast synchronize' , you got messages like 'partner is not synchronized. partner must be synchronized.' on both server1 and server2.

to solve this, I must remove the HA disk and reattach them without the initial synchronizing.

so, is this normal? any better idea?
must have at least one of the two partners be online ? :?: :D :D

Re: about HA, cannot resynchronize after shutdown both partners

Posted: Fri Jul 23, 2010 7:04 am
by Max (staff)
must have at least one of the two partners be online ?
Absolutely, what's the point of having HA then? :D
In case you need to perform maintenance or relocate the servers you need to disconnect both servers from the client side and remove the devices. Once you've turned everything back on, you just recreate the devices specifying "do not synchronize" initialization method.
However we're working on a fast sync option to be available after both nodes have been shut down.

Re: about HA, cannot resynchronize after shutdown both partners

Posted: Thu Sep 23, 2010 10:48 pm
by techtou
Hello Max!

Any news on that development (fast sync after both hosts down)?

Thanks,

Darko

Re: about HA, cannot resynchronize after shutdown both partners

Posted: Fri Sep 24, 2010 4:05 pm
by sberg
Is there a way to specify before or at Starwind startup that the local volumes are synchronized? That way when the other machine comes up it should do an automatic fast synch.

Re: about HA, cannot resynchronize after shutdown both partners

Posted: Sat Sep 25, 2010 8:56 pm
by Max (staff)
Hi all,
The news are there, and they're good!
Our developers are enabling this functionality in the upcoming 5.5 version, hang on, it will be out really soon :)