{"id":56285,"date":"2023-02-28T09:00:39","date_gmt":"2023-02-28T08:00:39","guid":{"rendered":"https:\/\/nolabnoparty.com\/?p=56285"},"modified":"2023-02-26T13:56:15","modified_gmt":"2023-02-26T12:56:15","slug":"starwind-vsan-journal-synchronization","status":"publish","type":"post","link":"https:\/\/nolabnoparty.com\/en\/starwind-vsan-journal-synchronization\/","title":{"rendered":"StarWind VSAN Journal Synchronization"},"content":{"rendered":"<p><img decoding=\"async\" class=\"aligncenter wp-image-56286 size-full\" title=\"starwind-vsan-journal-synchronization-01\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2023\/02\/starwind-vsan-journal-synchronization-01.jpg\" alt=\"starwind-vsan-journal-synchronization-01\" width=\"602\" height=\"202\" \/><\/p>\n<p><a href=\"https:\/\/nolabnoparty.com\/en\/starwind-linux-vsan-appliance\/\">StarWind VSAN<\/a> is the <strong>hyperconverged solution<\/strong> by StarWind that was further improved with the introduction of the Journal Synchronization feature.<\/p>\n<p>This new capability provides two important improvements:<!--more--><\/p>\n<ul>\n<li>Best performance<\/li>\n<li>Fast recovery<\/li>\n<\/ul>\n<p>In a typical StarWind VSAN deployment, the <strong>storage availability (HA)<\/strong> is ensured by the synchronous replication mechanism between the configured nodes making applications and services available 24\/7\/365 even in the event of a <strong>node failure<\/strong>.<\/p>\n<p>If a large capacity storage is deployed at the organization, it's clear the synchronization of a large amount of data <strong>can take a long time<\/strong> and a failure may cause the unavailability of some applications and services. This can be <strong>unacceptable by the business<\/strong> and a fast recovery strategy become the priority for the administrators. Here is where the Journal Synchronization comes into play.<\/p>\n<p>&nbsp;<\/p>\n<h2>Synchronous replication<\/h2>\n<p>In a typical vSAN deployment, synchronous replication mechanism is used to ensure that <strong>data is available in all nodes<\/strong> member of a specific cluster at the <strong>same time<\/strong>. The scope is assuring the <strong>storage redundancy<\/strong> to guarantee the maximum data availability in case one node experiences a failure.<\/p>\n<p>It may happen that during the synchronization especially with a large amount of data, a <strong>hardware or a software failure<\/strong> may affect the process with the result of having the replicated storage <strong>out of sync<\/strong>. In the worst situation, the storage itself <strong>can go offline<\/strong>. It's clear that the scenario where all nodes are not synchronized or offline, applications and services may fail (<em>picture from StarWind<\/em>).<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-56293 size-large\" title=\"starwind-vsan-journal-synchronization-02\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2023\/02\/starwind-vsan-journal-synchronization-02-600x132.jpg\" alt=\"starwind-vsan-journal-synchronization-02\" width=\"600\" height=\"132\" \/><\/p>\n<p>In addition, also the <strong>storage performance is affected<\/strong> because the synchronization process introduces an additional workload to the subsystem.<\/p>\n<p>&nbsp;<\/p>\n<h2>StarWind vSAN Journal Synchronization<\/h2>\n<p>The Journal Synchronization is the StarWind solution introduced in the recent update of VSAN that allows to <strong>minimize the risk of downtime<\/strong>. To minimize the time required for the synchronization, synchronization journals are <strong>stored on separate storage<\/strong> and <strong>sync only changes<\/strong> written to the storage while one of the partners was out of sync.<\/p>\n<p>This solution allows out of sync nodes to become <strong>available in minutes<\/strong> limiting the risk of service disruption maximizing the applications availability. The use of the Journal Synchronization process has a <strong>minimum impact on storage performance<\/strong> since nodes don't need to synchronize data which was already written on every node in the cluster (<em>picture from StarWind<\/em>).<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-56295 size-large\" title=\"starwind-vsan-journal-synchronization-03\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2023\/02\/starwind-vsan-journal-synchronization-03-600x329.jpg\" alt=\"starwind-vsan-journal-synchronization-03\" width=\"600\" height=\"329\" \/><\/p>\n<p>The new Journal Synchronization feature in the <a href=\"https:\/\/nolabnoparty.com\/en\/starwind-virtual-san-free\/\">StarWind VSAN<\/a> solution improves not only the storage performance but <strong>ensure fast recovery<\/strong> in case of problems occurred during the replication. Applications and services uptime are maximized bringing a <strong>big benefit to the business<\/strong>.<\/p>\n<p>StarWind VSAN is available to download as <a href=\"https:\/\/www.starwindsoftware.com\/starwind-virtual-san#demo\" target=\"_blank\" rel=\"noopener\">30-days trial<\/a>.<\/p>\n<p><img decoding=\"async\" title=\"signature\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/images\/firma.jpg\" alt=\"signature\" \/><\/p>\n","protected":false},"excerpt":{"rendered":"<p>StarWind VSAN is the hyperconverged solution by StarWind that was further improved with the introduction of the Journal Synchronization feature. This new capability provides two important improvements:<\/p>\n","protected":false},"author":3,"featured_media":56286,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rop_custom_images_group":[],"rop_custom_messages_group":[],"rop_publish_now":"initial","rop_publish_now_accounts":{"linkedin_93tdZWzMZc_93tdZWzMZc":"","facebook_2879994398731222_17841400390232720":"","twitter_113568041_113568041":"","mastodon_115463926174894442_115463926174894442":""},"rop_publish_now_history":[],"rop_publish_now_status":"pending","footnotes":""},"categories":[1787,903],"tags":[1668,2598,582,978,2039],"class_list":["post-56285","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-starwind-en","category-vmware-en","tag-hyperconverged","tag-journal","tag-replication-en","tag-synchronization-en","tag-vsan-en","has_thumb"],"_links":{"self":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/56285","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/comments?post=56285"}],"version-history":[{"count":0,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/56285\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media\/56286"}],"wp:attachment":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media?parent=56285"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/categories?post=56285"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/tags?post=56285"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}