{"id":433,"date":"2018-08-29T11:21:26","date_gmt":"2018-08-29T08:21:26","guid":{"rendered":"https:\/\/blog.arcak.net\/?p=410"},"modified":"2018-08-31T09:18:22","modified_gmt":"2018-08-31T06:18:22","slug":"vmware-vsan-2","status":"publish","type":"post","link":"https:\/\/blog.arcak.net\/index.php\/2018\/08\/29\/vmware-vsan-2\/","title":{"rendered":"VMware vSAN"},"content":{"rendered":"<p style=\"text-align: justify;\"><strong>VMware vSan<\/strong>\u00a0can be called as a technology that allows locally attached disks that are installed on the server to create a clustered disk space, or as <strong>Distributed Object-Based Storage<\/strong>. It reduces complexity eliminating the\u00a0 physical storage layer.<\/p>\n<p style=\"text-align: justify;\">Since\u00a0<strong>vSan<\/strong> is embedded in the hypervisor, what you need to do is only to activate it via\u00a0<strong>vSphere<\/strong> and a separate installation is not required.<\/p>\n<p style=\"text-align: justify;\">It can be taken as<strong> vSan ReadyNode<\/strong> from a variety of compatible vendors and make your own installation<strong>, <\/strong>Also can be taken\u00a0as ready-to-use solutions like <strong>Dell VxRail<\/strong>. You can also check whether your existing hardware is <strong>vSan<\/strong> compliant from <a href=\"https:\/\/www.vmware.com\/resources\/compatibility\/search.php?deviceCategory=vsan\"><strong>here<\/strong><\/a>\u00a0 and licensing for version 6.7 <strong><a href=\"https:\/\/www.vmware.com\/content\/dam\/digitalmarketing\/vmware\/en\/pdf\/products\/vsan\/vmware-vsan-67-licensing-guide.pdf\">here<\/a><\/strong><\/p>\n<p style=\"text-align: justify;\"><img loading=\"lazy\" decoding=\"async\" class=\"size-medium wp-image-423 aligncenter\" src=\"https:\/\/blog.arcak.net\/wp-content\/uploads\/2018\/08\/vsan-arch-300x201.png\" alt=\"\" width=\"300\" height=\"201\" srcset=\"https:\/\/blog.arcak.net\/wp-content\/uploads\/2018\/08\/vsan-arch-300x201.png 300w, https:\/\/blog.arcak.net\/wp-content\/uploads\/2018\/08\/vsan-arch-660x442.png 660w, https:\/\/blog.arcak.net\/wp-content\/uploads\/2018\/08\/vsan-arch.png 746w\" sizes=\"(max-width: 300px) 100vw, 300px\" \/><\/p>\n<p style=\"text-align: justify;\"><!--more--><\/p>\n<p style=\"text-align: justify;\">Technologies such as <strong>HA, DRS, vMotion <\/strong>used in <strong>VMware<\/strong> <strong>vSphere<\/strong> are compatible with <strong>vSan<\/strong>.<\/p>\n<p style=\"text-align: justify;\">A passthrough RAID card is required for <strong>vSan<\/strong>, so if you have an unsupported old card, there is still still a chance to install <strong>vSan <\/strong>by creating RAID-0 Virtual drives per each disk.<strong>\u00a0<\/strong>\u00a0(<strong>not recommended except for Test environment<\/strong>.)<\/p>\n<p style=\"text-align: justify;\">It can work in both hybrid and all-flash structure. For hybrid construction<strong>, <\/strong>Min. 1GB\/s network speed and\u00a0 Min. 10gb\/s for all-flash are required.<\/p>\n<p style=\"text-align: justify;\">Each disk group must consist of\u00a0<strong>1 cache SSD<\/strong> and\u00a0<strong>SSD<\/strong> or <strong>magnetic discs<\/strong> between\u00a0 1-7\u00a0 for capacity.\u00a0A total of<strong> 5 disk <\/strong>groups are supported.<\/p>\n<p style=\"text-align: justify;\">When used with All-flash, Nearline <strong>Deduplication<\/strong> and <strong>Compression<\/strong> are supported.<\/p>\n<p style=\"text-align: justify;\">Support for cabinet redundancy can be provided with <strong>Fault Domain<\/strong>.<\/p>\n<p style=\"text-align: justify;\">If the network access is not exceeding 5 ms latency, the loss of a location between two does not stop entire system from working with <strong>Stretched Cluster<\/strong> feature. The entire infrastructure will continue to operate over the second location. <strong>(Witness Node\u00a0 is required<\/strong>)<\/p>\n<p style=\"text-align: justify;\">Although vSan requires at least<strong> 3 <\/strong>node requirements to function, it can\u00a0also work with <strong>1 + 1<\/strong>\u00a0 i.e. <strong>2<\/strong> node using one Witness node.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"size-medium wp-image-431 aligncenter\" src=\"https:\/\/blog.arcak.net\/wp-content\/uploads\/2018\/08\/VSAN-Hardware-Build-Your-Own.png-1584\u00d7972-2018-08-29-13-46-08-300x140.png\" alt=\"\" width=\"300\" height=\"140\" srcset=\"https:\/\/blog.arcak.net\/wp-content\/uploads\/2018\/08\/VSAN-Hardware-Build-Your-Own.png-1584\u00d7972-2018-08-29-13-46-08-300x140.png 300w, https:\/\/blog.arcak.net\/wp-content\/uploads\/2018\/08\/VSAN-Hardware-Build-Your-Own.png-1584\u00d7972-2018-08-29-13-46-08-768x359.png 768w, https:\/\/blog.arcak.net\/wp-content\/uploads\/2018\/08\/VSAN-Hardware-Build-Your-Own.png-1584\u00d7972-2018-08-29-13-46-08-660x308.png 660w, https:\/\/blog.arcak.net\/wp-content\/uploads\/2018\/08\/VSAN-Hardware-Build-Your-Own.png-1584\u00d7972-2018-08-29-13-46-08.png 978w\" sizes=\"(max-width: 300px) 100vw, 300px\" \/><\/p>\n<p style=\"text-align: justify;\">Unlike the raid types in traditional storage units, <strong>Datastore default and virtual machine-based\u00a0<\/strong>RAID policies are used in <strong>vSan<\/strong>.<\/p>\n<p style=\"text-align: justify;\">Simply <strong>RAID1, RAID0, Ra\u0131d5-6 (Erasure Coding) <\/strong>variations of these policies including\u00a0<strong>Data locality and<\/strong>\u00a0<strong>Stretched Cluster <\/strong>exist in <strong>vSan<\/strong>. I&#8217;ll not keep it in detail for now, and will elaborate on my <a href=\"https:\/\/blog.arcak.net\/index.php\/en\/2018\/08\/30\/vmware-vsan-storage-policy-based-management-spbm\/\"><strong>next writings<\/strong><\/a>.<\/p>\n<p style=\"text-align: justify;\">\n","protected":false},"excerpt":{"rendered":"<p>VMware vSan\u00a0can be called as a technology that allows locally attached disks that are installed on the server to create a clustered disk space, or as Distributed Object-Based Storage. It reduces complexity eliminating the\u00a0 physical storage layer. Since\u00a0vSan is embedded in the hypervisor, what you need to do is only to activate it via\u00a0vSphere and [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[193,165,167],"tags":[],"class_list":["post-433","post","type-post","status-publish","format-standard","hentry","category-hyperconverged-infrastructure","category-virtualization","category-vmware"],"_links":{"self":[{"href":"https:\/\/blog.arcak.net\/index.php\/wp-json\/wp\/v2\/posts\/433"}],"collection":[{"href":"https:\/\/blog.arcak.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.arcak.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.arcak.net\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.arcak.net\/index.php\/wp-json\/wp\/v2\/comments?post=433"}],"version-history":[{"count":12,"href":"https:\/\/blog.arcak.net\/index.php\/wp-json\/wp\/v2\/posts\/433\/revisions"}],"predecessor-version":[{"id":507,"href":"https:\/\/blog.arcak.net\/index.php\/wp-json\/wp\/v2\/posts\/433\/revisions\/507"}],"wp:attachment":[{"href":"https:\/\/blog.arcak.net\/index.php\/wp-json\/wp\/v2\/media?parent=433"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.arcak.net\/index.php\/wp-json\/wp\/v2\/categories?post=433"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.arcak.net\/index.php\/wp-json\/wp\/v2\/tags?post=433"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}