Odd sync kicked off automatically

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

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

Post Reply
User avatar
mooseracing
Posts: 91
Joined: Mon Oct 11, 2010 11:55 am

Tue Feb 18, 2014 3:04 pm

I am in the process of upgrading to larger 72 disk cases from SM. I shut down one of our nodes (we run HA on two nodes), swapped the hardware into the new case, brought it back up the next day (today). Why would the node that has been up decided it needed to synchronize after this? It caused all of my VM's to crash since Hyper V was connected and running off the node that had been up.

Any logs I can post that would be useful? This is the first time, usually I can take one down without bothering Hyper V and it comes back up correctly as well.
User avatar
Max (staff)
Staff
Posts: 533
Joined: Tue Apr 20, 2010 9:03 am

Tue Feb 18, 2014 10:08 pm

Hi mooseracing!
I would recommend opening a support ticket at http://www.starwindsoftware.com/support-form
Or directly submitting an email to support@starwindsoftware.com
Our engineers will require System and Application Event logs, and StarWind logs from both machines.
You can attach them if the total size doesn't exceed 10 MBs. Usually this requires zipping.
This is the fastest way to get down to the bottom of the issue.
Max Kolomyeytsev
StarWind Software
Post Reply