We generally hear lot of use cases about storage running out of space in vSan and add new drives or scale up/out the servers. Have you ever thought of the environment that is over provisioned and hardware vendor is just charging hundreds of dollars per month for a drive, your
vSAN encryption was introduced in 6.6 to encrypt the data at both the drive levels i.e., cache and capacity disks that are part of a vSAN datastore. This is so easy to configure, do not require any in guest agents and supports hybrid, all flash , stretched cluster, dedup /
If you are familiar with thin vs thick provisioning disk, this post will help you understand much easier about the OSR (Object Space Reservation).
By default, virtual machine storage objects deployed on vSAN are thin provisioned. OSR is one of the storage policy, that specifies the percentage of the logical size
Striping is not a new word in storage world. In vSan, Striping splits the data of a given object into multiple stripes (drives), also known as segments but not necessarily multiple hosts.
Each stripe is accessed simultaneously, potentially increasing performance in hybrid configurations. vSAN allows for up to 12-way striping although 1
FTT is familiar name when working on vSAN and I consider this as most important policy when designing a vSan cluster. In this post, I am going to quickly walk you through the use of this policy and how it works..
The Number of Failures to Tolerate capability addresses the key
In continuation to my previous posts part1 and part2
In continuation to the previous post Part 1
RVC (Ruby Virtual console) is an interactive command-line console user interface for VMware vSphere and Virtual Center. It is bundled with both VCSA and the Windows version of vCenter Server. RVC is becoming one of the primary tools for managing and troubleshooting Virtual SAN environments.
Here are some of the RVC commands that
I would like to brief here about one of the rules in vSan storage policy i.e., Force Provisioning, it may sound very easy, but at times can put the environment in trouble.
Force provisioning is the rule which can be selected when creating a new storage policy as shown below: I
Stretched cluster to multi node vSan cluster
I assume most of you are aware about stretched cluster and how the component splits between the hosts/witness appliance. In this blog, I am going to walk you through the steps to convert a 2 vSan stretched cluster to a 3 node vSan cluster.
One node vSan cluster:
Have you tried building a one node vsan cluster ? or convert exiting multi node cluster to one node. Though its not recommended by VMware, it is possible to have one node vsan cluster but with limitations like no data protection as the single node cluster is
CLOMD value can be changed in multiple ways, here I am showing two ways i.e., powershell or cli
Take ssh to hosts in cluster and use below commands (6.x version) to fetch the clomd values and change the values:
esxcfg-advcfg --get /VSAN/ClomRepairDelay
When working on lab environment, I got an idea of changing the complete vSan subnet for hosts and immediately started working on it without waiting a minute, with paper work first , before implementing it and finally ended with a success..
Here is my lab environment details:
No of hosts in
Recently I have got a request to convert the multi node vsan cluster (3 hosts) to stretched cluster (2 hosts + 1 witness). Since this is for a production environment with FTT 1, I planned this in two phases:
1. Deploy the witness appliance with all necessary licensing, networking, routing