The Latest Gartner® Magic Quadrant™Hyperconverged Infrastructure Software
Moderators: anton (staff), art (staff), Anatoly (staff), Max (staff)
Aitor_Ibarra wrote:Aside to above: until today I was doing a reliability test. 20100831 passed with flying colours.
For 6 days and 1 hour I've been testing using Bart's Stuff Test. Target was HA, WT cache, auto-resync. The test writes and verifies randomly generated data. Over the test period, 5.4TB was written and verified. Each Starwind node was set to reboot itself once per hour, with 30 mins between each node, so in the test period there were 145 reboots per node, therefore 290 resyncs. No problems whatsoever.
If you are running Windows 2008 R2 on either the host or the client, and you get a BSOD, look in the windows logs - you will find that the windows iSCSI initiator was the clulprit. There is a hotfix from Microsoft which cured this for me. It is documented as being aimed at issues with booting from iSCSI, but whatever it does, it has fixed my BSOD issues. See http://support.microsoft.com/kb/979711/en-gb. Starwind HA uses the windows iSCSI initiator for sync; so as far as I'm concerned, this was a Microsoft bug rather than a Starwind one.
cheers,
Aitor
The size is exactly what I want to know! So that if I ever get a period of extended downtime, I have an idea of when a fast sync is not going to be possible, as full syncs would need to be scheduled to a less disruptive time.If the fast sync log data size have achieved this size, full synchronization is executed too.