{"id":1123,"date":"2013-09-05T23:16:09","date_gmt":"2013-09-05T22:16:09","guid":{"rendered":"http:\/\/www.bussink.ch\/?p=1123"},"modified":"2018-05-23T17:57:19","modified_gmt":"2018-05-23T15:57:19","slug":"homelab-with-vsphere-5-5-and-vsan","status":"publish","type":"post","link":"https:\/\/www.bussink.ch\/?p=1123","title":{"rendered":"Homelab with vSphere 5.5 and VSAN"},"content":{"rendered":"

This is to give you a quick insight in my 2013 Homelab that is running vSphere 5.5 and has a running version of Virtual SAN (VSAN) in Beta code. I have been quiet on the blog for a while, as I’ve been doing some tests with vSphere 5.5 and VSAN, but the NDA has limited my communications.<\/p>\n

This is probably the smallest VSAN implementation you can do without going with a Nested VSAN<\/a> (Awesome design by William Lam) or with three Mac Mini’s.<\/p>\n

This VSAN is only 24cm x 22cm x 20cm (High x Depth x Width), and runs with 130 Watts total consumption. On the following screenshot you see the Homelab next to an old Synology DS1010+<\/p>\n

\"Homelab<\/a>

Homelab running vSphere 5.5 with VSAN<\/p><\/div>\n

 <\/p>\n

It is composed of three Shuttle XH61v with a quad-core i7-3770s<\/a> processor (65W) and 16GB of memory (Two 8GB Kingston SO-DIMM). The Shuttle XH61v also comes with two Gigabit network cards. Each Shuttle XH61v has the following storage<\/p>\n

    \n
  1. Kingston USB 3.0 DataTraveller 16GB Key to boot vSphere 5.5<\/li>\n
  2. Intel mSATA 525 SSD 120GB which is used by vFlash<\/li>\n
  3. Intel 530 SSD 240GB 2.5″ or Samsung 840 Pro 256GB<\/li>\n
  4. Seagate Momentus HD 2.5″ 750GB 7200rpm<\/li>\n<\/ol>\n

    That is a lot of storage in such a small case, but it works, and you don’t even hear the ventilator (for Wife Acceptance Factor approval).<\/p>\n

    I’m not going to cover in this article how you need to create a VMkernel interface for VSAN, and that you need to disable HA before turning VSAN on. This article “VSAN How to Configure<\/a>” by David Hill does an excellent job, and his follow-up post “Configure disk redundancy in VSAN<\/a>” adds more information.<\/p>\n

    From the vSphere Web Client, this is the configuration of my VSAN after I enabled it.<\/p>\n

    \"VSAN<\/a>

    VSAN Disk Management<\/p><\/div>\n

    So once you enable the VSAN with three hosts that each have an empty SSD and HD (in my case 240GB SSD and 750GB HD) you get the following.<\/p>\n

    \"VSAN<\/a>

    VSAN Datastore created<\/p><\/div>\n

    Another great functionality of the VSAN, is that if you take another ESXi host and configure it’s VSAN VMkernel interface and add it to the VSAN Resource, it automaticaly mounts the VSAN Datastore. This will greatly simplify the provisioning of storage in a vSphere Cluster. The VSAN Datastore is also the first implementation of Virtual Volumes (VVOL) that I have seen. Cormac Hogan has a great Virtual Volume (VVOL) Tech Preview<\/a> article.<\/p>\n

    The Virtual SAN from VMware should be available in Beta for a wider audience very soon, so go over to VMware VSAN Beta Register<\/a>.<\/p>\n

     <\/p>\n