<?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=VMware%2FVirtual_SAN</id>
	<title>VMware/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=VMware%2FVirtual_SAN"/>
	<link rel="alternate" type="text/html" href="https://aznot.com/index.php?title=VMware/Virtual_SAN&amp;action=history"/>
	<updated>2026-05-08T19:46:24Z</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=VMware/Virtual_SAN&amp;diff=2127&amp;oldid=prev</id>
		<title>Kenneth: Created page with &quot;== VSAN ==  Virtual SAN is a software-based storage solution built into the hypervisor that aggregates the hosts&#039; local storage devices (SSD and HDD) and makes them appear as...&quot;</title>
		<link rel="alternate" type="text/html" href="https://aznot.com/index.php?title=VMware/Virtual_SAN&amp;diff=2127&amp;oldid=prev"/>
		<updated>2015-05-06T02:17:34Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;quot;== VSAN ==  Virtual SAN is a software-based storage solution built into the hypervisor that aggregates the hosts&amp;#039; local storage devices (SSD and HDD) and makes them appear as...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;== VSAN ==&lt;br /&gt;
&lt;br /&gt;
Virtual SAN is a software-based storage solution built into the hypervisor that aggregates the hosts&amp;#039; local storage devices (SSD and HDD) and makes them appear as a single pool of storage shared across all hosts.&lt;br /&gt;
&lt;br /&gt;
== Feature Highlights ==&lt;br /&gt;
&lt;br /&gt;
Virtual SAN provides the following capabilities:&lt;br /&gt;
* Automated Storage Management via Intelligent VM based policies&lt;br /&gt;
* Dynamic scalability to grow storage and compute dynamically on an as-needed basis&lt;br /&gt;
* Integrated with vSphere and managed in vCenter&lt;br /&gt;
* Built-in resiliency with protection from multiple hardware failures&lt;br /&gt;
* Per-VM with SLA management via intelligent data placement&lt;br /&gt;
* Instant storage provisioning without complex workflows&lt;br /&gt;
&lt;br /&gt;
Hardware Compatibility / Setup Requirements&lt;br /&gt;
* Minimum 3 vSphere Hosts with storage&lt;br /&gt;
* Combination of SAS/SATA HDD &amp;amp; SSD; at least 1 SSD and 1 HDD in every host contributing storage to the cluster&lt;br /&gt;
* SAS/SATA RAID Controller: Must work in “pass-thru” or “HBA” mode (e.g. LSI 2008)&lt;br /&gt;
* ESXi boot: SD card/USB/SATADOM is preferred (ESXi boot partition and Virtual SAN cannot co-exist on the same SSD/HDD)&lt;br /&gt;
* Network: 10G (preferred)&lt;br /&gt;
&lt;br /&gt;
== Licensing ==&lt;br /&gt;
&lt;br /&gt;
vSAN will require seperate licensing from the Hosts and vCenter Server.&lt;br /&gt;
&lt;br /&gt;
&amp;quot;When you enable Virtual SAN on a cluster, you must assign the cluster an appropriate Virtual SAN license before its 60-day evaluation period expires. Just like vSphere licenses, Virtual SAN licenses have per CPU capacity. When you assign a Virtual SAN license to a cluster, the amount of license capacity that is used equals the total number of CPUs in the hosts that participate in the cluster. For example, if you have a Virtual SAN cluster that contains four hosts with eight CPUs each, you need to assign the cluster a Virtual SAN license with a minimum capacity of 24 CPUs.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
References:&lt;br /&gt;
* vSphere 5.5 Documentation Center - http://pubs.vmware.com/vsphere-55/index.jsp?topic=%2Fcom.vmware.vsphere.vcenterhost.doc%2FGUID-31AADB51-799C-40C2-882C-8D71B31C4BB9.html&lt;br /&gt;
&lt;br /&gt;
== Setup ==&lt;br /&gt;
&lt;br /&gt;
Need at least 3 hosts, each with at least 1 free SSD and 1 free non-SSD.  Additional hosts can be added as storage or as compute nodes.&lt;br /&gt;
&lt;br /&gt;
Each SSD / non-SSD needs to be formatted clean, or at least have all partitions removed.&lt;br /&gt;
 partedUtil get /dev/disks/eui.00000000000000&lt;br /&gt;
 partedUtil delete /dev/disks/eui.00000000000000 1&lt;br /&gt;
&lt;br /&gt;
Each host will need to have a vmKernel interface configured for vSAN.  All of which will need to be on the same subnet.&lt;br /&gt;
&lt;br /&gt;
== Command Line ==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
# esxcli vsan&lt;br /&gt;
&lt;br /&gt;
Available Namespaces:&lt;br /&gt;
  datastore             Commands for VSAN datastore configuration&lt;br /&gt;
  network               Commands for VSAN host network configuration&lt;br /&gt;
  storage               Commands for VSAN physical storage configuration&lt;br /&gt;
  cluster               Commands for VSAN host cluster configuration&lt;br /&gt;
  maintenancemode       Commands for VSAN maintenance mode operation&lt;br /&gt;
  policy                Commands for VSAN storage policy configuration&lt;br /&gt;
  trace                 Commands for VSAN trace configuration&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Set auto mode:&lt;br /&gt;
 esxcli vsan storage automode set --enabled=&amp;quot;false&amp;quot;&lt;br /&gt;
&lt;br /&gt;
List vSAN storage on local host:&lt;br /&gt;
 esxcli vsan storage list&lt;br /&gt;
&lt;br /&gt;
Get vSAN datastore name:&lt;br /&gt;
 esxcli vsan datastore name get&lt;br /&gt;
&lt;br /&gt;
Remove local disk from vSAN datastore:&lt;br /&gt;
 esxcli vsan storage remove --disk mpx.vmhba2:C0:T1:L0&lt;br /&gt;
 esxcli vsan storage remove --ssd mpx.vmhba2:C0:T1:L0&lt;br /&gt;
 esxcli vsan storage remove --uuid 52afa1de-4240-d5d6-17f9-8af1ec8509e5&lt;br /&gt;
&lt;br /&gt;
Leave cluster:&lt;br /&gt;
 esxcli vsan cluster leave&lt;br /&gt;
&lt;br /&gt;
References:&lt;br /&gt;
* vSAN command line | VMware Communities - http://communities.vmware.com/message/2245973&lt;br /&gt;
&lt;br /&gt;
== VM Storage Policy ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Number of disk stripes per object: (1-12:1)&amp;#039;&amp;#039;&amp;#039;&amp;lt;br/&amp;gt;&lt;br /&gt;
The number of HDDS across which each replica of a storage object is striped.&lt;br /&gt;
A value higher than 1 may result in better performance (for e.g. when flash&lt;br /&gt;
reach cache misses need toget services from HDD), but also results in higher&lt;br /&gt;
use of system resources.&lt;br /&gt;
Default value: 1, Maximum value: 12.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Number of failures to tolerate: (0-3:1)&amp;#039;&amp;#039;&amp;#039;&amp;lt;br/&amp;gt;&lt;br /&gt;
Defines the number of host, disk or network failures a storage object can&lt;br /&gt;
tolerate. For n failures tolerated, &amp;quot;n+1&amp;quot; copies of the object are created and&lt;br /&gt;
&amp;quot;2n+1&amp;quot; hosts contributing storage are required.&lt;br /&gt;
Default value: 1, Maximum value: 3.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Flash read cache reservation (%): (0-100:0.0)&amp;#039;&amp;#039;&amp;#039;&amp;lt;br/&amp;gt;&lt;br /&gt;
Flash capacity reserved as read cache for the storage object. Specified as a&lt;br /&gt;
percentage of the logical size of the object. To be used only for addressing&lt;br /&gt;
read performance issues. Reserved flash capacity cannot be used by other&lt;br /&gt;
objects. Unreserved flash is shared faily among all objects.&lt;br /&gt;
Default value: 0%, Maximum value: 100%.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Force provisioning: (No-Yes:No)&amp;#039;&amp;#039;&amp;#039;&amp;lt;br/&amp;gt;&lt;br /&gt;
If this option is &amp;quot;Yes&amp;quot;, the object will be provisioned even if the policy&lt;br /&gt;
specified in the storage policy is not satisfiable with the resources currently&lt;br /&gt;
available in the cluster.  VSAN will try to bring the object into compliance if&lt;br /&gt;
and when resources become available.&lt;br /&gt;
Default Value: No.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Object space reservation: (0-100:0)&amp;#039;&amp;#039;&amp;#039;&amp;lt;br/&amp;gt;&lt;br /&gt;
Percentage of the logical size of the storage object that will be reserved&lt;br /&gt;
(thick provisioned) upon VM provisioning. The rest of the storage object in&lt;br /&gt;
thin provisioned.&lt;br /&gt;
Default value: 0%, Maximum value: 100%.&lt;br /&gt;
&lt;br /&gt;
Error:&lt;br /&gt;
 The policy requires 2 replicas with 2 disks each with&lt;br /&gt;
 0 bytes free each.  Only found 0 such disks.&lt;br /&gt;
&lt;br /&gt;
== HCL ==&lt;br /&gt;
&lt;br /&gt;
VSAN HCL - http://vmwa.re/vsanhcl&lt;br /&gt;
&lt;br /&gt;
VSAN HCL - http://www.vmware.com/resources/compatibility/search.php?deviceCategory=vsan&lt;br /&gt;
&lt;br /&gt;
References:&lt;br /&gt;
* VSAN and the AHCI controller (hint: not supported!) - http://feedproxy.google.com/~r/YellowBricks/~3/JoubaeDiX_k/&lt;br /&gt;
&lt;br /&gt;
== Pricing ==&lt;br /&gt;
&lt;br /&gt;
$2,495 per CPU or $14,970 for a standard 3 node (2 CPU each) cluster.&lt;br /&gt;
&lt;br /&gt;
VMware VSAN License Calculator | Virten.net - http://www.virten.net/2014/03/vmware-vsan-license-calculator/&lt;br /&gt;
&lt;br /&gt;
VMware Virtual SAN Now Available | VMware Company Blog - VMware Blogs - http://blogs.vmware.com/vmware/?p=2311&lt;br /&gt;
&lt;br /&gt;
VMware Virtual SAN Licensing and Pricing | Virten.net - http://www.virten.net/2014/03/vmware-virtual-san-licensing-and-pricing/&lt;br /&gt;
&lt;br /&gt;
http://blogs.vmware.com/vmware/files/2014/03/Virtual-SAN-5.5-Pricing-Packaging1.png&lt;br /&gt;
&lt;br /&gt;
== Beta ==&lt;br /&gt;
&lt;br /&gt;
VMware Communities: Welcome to the vCloud Suite Beta Program - http://communities.vmware.com/community/vmtn/beta/vcloud_suite?view=documents&lt;br /&gt;
* VMware Communities: vSAN Workflows for Hosted Beta Only - http://communities.vmware.com/docs/DOC-22252&lt;br /&gt;
&lt;br /&gt;
---&lt;br /&gt;
&lt;br /&gt;
Coming in Beta2 Refresh - http://communities.vmware.com/servlet/JiveServlet/previewBody/22898-102-1-30527/Coming%20in%20Beta2%20Refresh.pdf&lt;br /&gt;
&lt;br /&gt;
Released: Monday, April 29th, 2013.&lt;br /&gt;
&lt;br /&gt;
== Issues ==&lt;br /&gt;
&lt;br /&gt;
=== storage policy 2 of 3 contributing ===&lt;br /&gt;
&lt;br /&gt;
Error:&lt;br /&gt;
 Cannot complete file creation operation.&lt;br /&gt;
 The policy requires 3 hosts contributing storage, only found 2 in the cluster.&lt;br /&gt;
 Failed to create object.&lt;br /&gt;
&lt;br /&gt;
=== storage policy 2 replicas ===&lt;br /&gt;
&lt;br /&gt;
Error:&lt;br /&gt;
 Cannot complete file creation operation.&lt;br /&gt;
 The policy requires 2 replicas with 1 disks each with 0 bytes free each.  Only found 0 such disks.&lt;br /&gt;
 Failed to create object.&lt;br /&gt;
&lt;br /&gt;
== keywords ==&lt;br /&gt;
&lt;br /&gt;
[[Category:VMware]]&lt;/div&gt;</summary>
		<author><name>Kenneth</name></author>
	</entry>
</feed>