<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://aznot.com/index.php?action=history&amp;feed=atom&amp;title=VMworld_2015%2FBuilding_a_Stretched_Cluster_with_Virtual_SAN</id>
	<title>VMworld 2015/Building a Stretched Cluster with Virtual SAN - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://aznot.com/index.php?action=history&amp;feed=atom&amp;title=VMworld_2015%2FBuilding_a_Stretched_Cluster_with_Virtual_SAN"/>
	<link rel="alternate" type="text/html" href="https://aznot.com/index.php?title=VMworld_2015/Building_a_Stretched_Cluster_with_Virtual_SAN&amp;action=history"/>
	<updated>2026-05-09T00:13:22Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.41.0</generator>
	<entry>
		<id>https://aznot.com/index.php?title=VMworld_2015/Building_a_Stretched_Cluster_with_Virtual_SAN&amp;diff=2454&amp;oldid=prev</id>
		<title>Kenneth at 18:58, 1 September 2015</title>
		<link rel="alternate" type="text/html" href="https://aznot.com/index.php?title=VMworld_2015/Building_a_Stretched_Cluster_with_Virtual_SAN&amp;diff=2454&amp;oldid=prev"/>
		<updated>2015-09-01T18:58:43Z</updated>

		<summary type="html">&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;== Building a Stretched Cluster with Virtual SAN ==&lt;br /&gt;
&lt;br /&gt;
By Duncan Epping and Rawlinson Rivera (VMware)&lt;br /&gt;
&lt;br /&gt;
“A stretched cluster is a deployment model in which two or more virtualization host servers are part of the same logical cluster but are located in separate geographical locations.”&lt;br /&gt;
&lt;br /&gt;
Metro Clusters&lt;br /&gt;
&lt;br /&gt;
vSphere + Virtual SAN – Stretched Cluster&lt;br /&gt;
&lt;br /&gt;
Fault Domains – (data, data, witness)&lt;br /&gt;
&lt;br /&gt;
Virtual SAN cluster is formed across the 3 fault domains (sites or datacenters)&lt;br /&gt;
&lt;br /&gt;
Requirements:&lt;br /&gt;
*	Network:&lt;br /&gt;
**	Virtual SAN storage networking&lt;br /&gt;
**	Virtual SAN witness networking&lt;br /&gt;
**	vSphere and virtual machine networking&lt;br /&gt;
**	10 Gbps connectivity or greater&lt;br /&gt;
**	&amp;lt; 5 millisecond latency RTT&lt;br /&gt;
**	Multicasting&lt;br /&gt;
*	Storage:&lt;br /&gt;
**	Virtual machine storage&lt;br /&gt;
**	Witness appliance storage&lt;br /&gt;
*	Compute:&lt;br /&gt;
**	Virtual SAN witness&lt;br /&gt;
**	vSphere HA&lt;br /&gt;
**	vSphere DRS&lt;br /&gt;
&lt;br /&gt;
Witness only stores metadata.  Communication to it is minimal.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Steps to build a stretch cluster:&lt;br /&gt;
*	Configure Fault Domains&lt;br /&gt;
*	Select Witness Host&lt;br /&gt;
*	?&lt;br /&gt;
*	?&lt;br /&gt;
&lt;br /&gt;
Virtual Machine Monitoring – the core of the heart beating for HA&lt;br /&gt;
*	If doing maintenance, disable this&lt;br /&gt;
&lt;br /&gt;
Reserved failover capacity resources – set to 50% (yes you lose half your resources!)&lt;br /&gt;
&lt;br /&gt;
Test Test Test - Test all of the various failure scenarios you can have&lt;br /&gt;
* Network partition between data sites&lt;br /&gt;
* Full site failure&lt;br /&gt;
* Witness site failure&lt;br /&gt;
&lt;br /&gt;
---&lt;br /&gt;
&lt;br /&gt;
Announcing:&lt;br /&gt;
* 2-Node Remote Office Branch Office Solution&lt;br /&gt;
&lt;br /&gt;
Captain VSAN&lt;/div&gt;</summary>
		<author><name>Kenneth</name></author>
	</entry>
</feed>