VMware

vSAN File Services and hybrid performance with large cache drives?

vSAN File Services and hybrid performance with large cache drives?



View Reddit by jdp83View Source

 

To see the full content, share this page by clicking one of the buttons below

Related Articles

One Comment

  1. FWIW, You’re probably not getting many responses because your post is a mess to read.

    My thoughts in response to your post:

    * File services is still in beta.

    * You definitely shouldn’t be putting your ZFS pool on top of VMDKs on vSAN. FreeNAS will not like this at all. But there’s nothing wrong with putting your FreeNAS boot disk on vSAN, then passing through an HBA for your pool disks (ideal), or using RDMs for the same.

    * I’m having difficulty understanding the concern you’re trying to convey regarding growing a ‘main disk’. I’m not sure what you mean by ‘main disk’. I’m even more confused by your following concern that “creatinga dditional virtual disks on the same underlying hardware” will “tax the system more”. Please elaborate?

    * I cannot emphasize how important it is to have storage controllers and disks that are on the vSAN HCL/compatibility guide, and NICs that are on the vSphere compatibility guide. All of them need to use driver and firmware versions specified in these guides. I would not trust a vSAN implementation that uses off-HCL components, particularly with data I cared about.

    * You state that you want to mix 3 different sizes of capacity tier HDDs in the cluster. This is a bad idea. Though it will work, you will inevitably run into performance and balance issues. The key to successful vSAN cluster design is *balance*. Use identically cache and capacity devices in each of your disk groups.

    * You can run multiple disk groups on the same HBA.

    * I would recommend running your third host as a standalone ESXi host, and deploy the virtual witness appliance to it, so that you can do a proper 2-node vSAN deployment with your other two hosts. Do not nest your virtual witness inside the vSAN cluster, and don’t try to add your 3rd physical host to the vSAN cluster without any vSAN disk groups (you wouldn’t even be able to satisfy the default storage policy).

Leave a Reply