Status of feature "avoid full syncs after outages"

[MIT]

Heyho,

in https://forums.starwindsoftware.com/vie ... f=5&t=5277
you mentioned
"The build that helps users to avoid full syncs after outages should be available soon (rough ETA is in 2-3 builds). Check StarWind Release notes. Stay tuned!"
https://forums.starwindsoftware.com/vie ... 277#p33101

That was 2021-10.
The last changelog on vSAN for HyperV is 2021-11.

The two changelogs don't mention said feature...
Skimmed the blogs, nothing...
Beta forum, nope...

I'm very much looking forward to something like this to be able to better automate patching.
And even aside from that, should we ever run into some "proper issue/defect" in production, this would greatly ease the recovery (might just be a short network issue for example).

So if possible, an update would be great

[yaroslav (staff)]

Please stay tuned. It should arrive in the upcoming builds.

[MIT]

Well is there a rough estimate when these builds might hit production?
*Rough* is totally fine with me.

But currently it could be 2024 and "stay tuned" becomes somewhat of a joke in that case
Because nobody reads "soon (rough ETA is in 2-3 builds)" as "over a year", at least by default.

[yaroslav (staff)]

Unfortunately, there is no clear ETA now for this very feature to be implemented.
It should be sometime mid-Q1 next year.

[MIT]

Thanks!

[yaroslav (staff)]

You are always welcome. Please keep an eye on the release notes.

[FlashMe]

New version of StarWind VSAN for Hyper-v was released today.

https://www.starwindsoftware.com/release-notes-build

We will see how it will run

"Added synchronization journal places on a disk with two working strategies:
Best Performance: The strategy provides better I/O performance while all device nodes are in a healthy state. But it can't guarantee fast synchronization in all cases.
Fast Recovery: The strategy provides faster recovery in all cases but requires an I/O overhead for each write operation."

[yaroslav (staff)]

Yup. Please keep us posted on how it goes

[MIT]

Due to internal delays we only came back to this yesterday...

Good for us, anyway

Using Version V8 (build 15159) 08 June 2023
Fixed failure when extending StarWind HA device with disk-based synchronization journal.

We opted for https://knowledgebase.starwindsoftware. ... a-devices/

Continuous journal
That setting uses a disk-based journal continuously which ensures fast synchronization and data consistency in all cases. This approach has the worst I/O performance, because of frequent write operations to the disk-based journal.

With no services running aside from MS Failover CSV I copied an ISO to the CSV and during the process just went and shut down one of the two nodes.
After coming back up, the sync was basically instant - as opposed to 15-20m for our SSD device and 2-3h for our HDD device, if it would have been a full sync.

So... works great?!

We'll definitely (ab)use this for intraday maintenance

[yaroslav (staff)]

The continuous journal is a cool feature, yet performance impact due to double-writing to disks might require NVMe or SSD (C:\ might also work) for sync journals.