{"id":521,"date":"2018-09-01T21:09:15","date_gmt":"2018-09-01T18:09:15","guid":{"rendered":"https:\/\/blog.arcak.net\/?p=509"},"modified":"2018-09-01T22:51:27","modified_gmt":"2018-09-01T19:51:27","slug":"vsan-fault-domain-2","status":"publish","type":"post","link":"https:\/\/blog.arcak.net\/index.php\/2018\/09\/01\/vsan-fault-domain-2\/","title":{"rendered":"VMware vSAN Fault Domain"},"content":{"rendered":"<p style=\"text-align: justify;\">In this article I will explain the subject of <strong>vSAN Fault Domains<\/strong>. You can review the original source <a href=\"https:\/\/docs.vmware.com\/en\/VMware-vSphere\/6.7\/com.vmware.vsphere.virtualsan.doc\/GUID-8491C4B0-6F94-4023-8C7A-FD7B40D0368D.html\"><strong>here<\/strong><\/a>.<\/p>\n<p style=\"text-align: justify;\"><strong>Fault Domains<\/strong>\u00a0allow systems to run in cases where multiple server failures or a cabinet is not reachable by spreading the <strong>vSAN<\/strong> cluster across multiple cabinets or blade chassis. One or more servers can be added to each Fault Domain.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"size-medium wp-image-514 aligncenter\" src=\"https:\/\/blog.arcak.net\/wp-content\/uploads\/2018\/09\/Fault-Domain-300x172.png\" alt=\"\" width=\"300\" height=\"172\" srcset=\"https:\/\/blog.arcak.net\/wp-content\/uploads\/2018\/09\/Fault-Domain-300x172.png 300w, https:\/\/blog.arcak.net\/wp-content\/uploads\/2018\/09\/Fault-Domain.png 400w\" sizes=\"(max-width: 300px) 100vw, 300px\" \/><\/p>\n<p><!--more--><\/p>\n<p style=\"text-align: justify;\">The <strong>Primary level of failures to tolerate (PFTT) <\/strong>policy in <strong>vSan<\/strong> cluster depends on the number of failure that the virtual machine can tolerate. When <strong>PFTT<\/strong> <strong>= 1<\/strong> is defined, any single failure can be recovered\u00a0in <strong>vSan Fault Domain<\/strong> <strong>(e.g. entire cabinet failure)<\/strong>.<\/p>\n<p style=\"text-align: justify;\">When a virtual server is provisioned after\u00a0fault domains are configured<strong>,<\/strong> the protection objects such as <strong>vSAN<\/strong>, replica, and<strong> witness\u00a0<\/strong>are\u00a0stored in different fault domains. If the storage-based policy is<strong> PFTT<\/strong> = <strong>N<\/strong>, <strong>vSAN<\/strong>\u00a0requires at least <strong>2n + 1\u00a0<\/strong>number of <strong>Fault Domains<\/strong>. If the virtual machines in the <strong>vSAN<\/strong> cluster use the <strong>Fault Domain<\/strong> policy, the corresponding virtual machine objects are kept in different cabinets.<\/p>\n<p style=\"text-align: justify;\">In the same way as the vSphere cluster with three nodes<strong>, <\/strong>it needs min. <strong>3 units (2 * 1 + 1) Fault Domain <\/strong>in order to provide <strong>PFTT = 1<\/strong>.<\/p>\n<p style=\"text-align: justify;\">If a cabinet is not fully accessible then a high percentage of hardware resources are lost thus it is recommended to create small <strong>Fault Domains<\/strong> to minimize the impact.<\/p>\n<p style=\"text-align: justify;\">The following Best Practises should be followed while working with <strong>Fault domains<\/strong>;<\/p>\n<ul style=\"text-align: justify;\">\n<li><strong>min. 3<\/strong> and for best results\u00a0<strong>4<\/strong> and <strong>more<\/strong> <strong>Fault domains<\/strong> should be created in a <strong>vSAN<\/strong> cluster.<\/li>\n<li>A server that does not belong to any fault domain is considered as its own\u00a0single-server fault domain.<\/li>\n<li>When servers in the <strong>vSAN<\/strong> are moved to different clusters, they continue to retain the <strong>Fault Domain<\/strong> properties they belong to.<\/li>\n<li>Each<strong>\u00a0vSAN<\/strong>\u00a0host is not required to be assigned to a <strong>Fault Domain<\/strong>, and if possible, fault domains of equal sizes must be configured.<\/li>\n<li>When designing a <strong>Fault Domain<\/strong>, it is recommended to approach from both disk and compute power perspective with peer servers.<\/li>\n<li>A desired number of servers can be added to a Fault Domain in a minimum of 1.<\/li>\n<\/ul>\n<p style=\"text-align: justify;\">The next spell will be Stretched Cluster, you can reach it <a href=\"https:\/\/blog.arcak.net\/index.php\/en\/2018\/09\/01\/vmware-vsan-stretched-cluster-2\/\"><strong>here<\/strong><\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In this article I will explain the subject of vSAN Fault Domains. You can review the original source here. Fault Domains\u00a0allow systems to run in cases where multiple server failures or a cabinet is not reachable by spreading the vSAN cluster across multiple cabinets or blade chassis. One or more servers can be added to [&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-521","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\/521"}],"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=521"}],"version-history":[{"count":6,"href":"https:\/\/blog.arcak.net\/index.php\/wp-json\/wp\/v2\/posts\/521\/revisions"}],"predecessor-version":[{"id":529,"href":"https:\/\/blog.arcak.net\/index.php\/wp-json\/wp\/v2\/posts\/521\/revisions\/529"}],"wp:attachment":[{"href":"https:\/\/blog.arcak.net\/index.php\/wp-json\/wp\/v2\/media?parent=521"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.arcak.net\/index.php\/wp-json\/wp\/v2\/categories?post=521"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.arcak.net\/index.php\/wp-json\/wp\/v2\/tags?post=521"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}