Category Archives: Virtual SAN

Scaling out your vSAN File Services Cluster


Advertise here with BSA

This week I have been testing with vSAN File Services and one of the procedures I wanted to run through was scaling out my vSAN File Services cluster. In my case, I have a cluster of 5 hosts and what I want to do is add a host to my vSAN cluster, expand the vSAN […] Continue reading

Posted in 7, 7.0, file services, Server, Software Defined, Storage, Virtual SAN, VMware, vsan, vsan fs | Comments Off on Scaling out your vSAN File Services Cluster

ESXTOP in vSphere 7


Advertise here with BSA

I was playing around with Scalable Shares and then noticed some enhancements in esxtop which I didn’t realize were there. I figured I would list the changes I spotted so people are aware of what was added to esxtop in vSphere 7.0. Although it isn’t a huge amount, it is still very valuable to know! […] Continue reading

Posted in esxtop, Server, Storage, Virtual SAN, vSphere, vsphere 7 | Comments Off on ESXTOP in vSphere 7

Creating a vSAN 7.0 Stretched Cluster


Advertise here with BSA

A while ago I wrote this article and created this demo showing the creation of a vSAN Stretched Cluster. I bumped into the article/video today when I was looking for something and figured that it is time to recreate the vSAN Stretched Cluster demo. I recorded it today, using vSphere / vSAN 7, and just […] Continue reading

Posted in 7, 7.0, BC-DR, Software Defined, Storage, stretched cluster, Virtual SAN, VMware, VMware Cloud Foundation, vsan, vSphere | Comments Off on Creating a vSAN 7.0 Stretched Cluster

vSAN/DRS awareness to be introduced in vSAN/vSphere 7.0!


Advertise here with BSA

It was briefly mentioned here, but I figured I would elaborate on this new cool feature for vSAN Stretched Clusters which is DRS Awareness of vSAN Stretched Clusters. So what does this mean? Well, it is fairly straight forward. DRS will take vSAN resync traffic into consideration when the DRS algorithm runs. I can probably […] Continue reading

Posted in 7, 7.0, BC-DR, drs, Server, Software Defined, Storage, stretched cluster, Virtual SAN, VMware, VMware Cloud Foundation, vsan | Comments Off on vSAN/DRS awareness to be introduced in vSAN/vSphere 7.0!

Introducing vSAN File Services as part of vSAN 7.0


Advertise here with BSA

There was a great article by Cormac talking about vSAN File Services published last week. I had some articles planned, but hadn’t started yet, so when I saw the article I figured I would do something different. No point in rehashing what Cormac has already shared right. I figured I would shoot another demo, and […] Continue reading

Posted in file services, Server, Software Defined, Storage, Various, Virtual SAN, VMware, VMware Cloud Foundation, vsan, vsan 7, vsan file services, vsphere 7 | Comments Off on Introducing vSAN File Services as part of vSAN 7.0

Can I still provision VMs when a vSAN Stretched Cluster site has failed? Part II


Advertise here with BSA

3 years ago I wrote the following post: Can I still provision VMs when a VSAN Stretched Cluster site has failed? Last week I received a question on this subject, and although officially I am not supposed to work on vSAN in the upcoming three months I figured I could test this in the evening […] Continue reading

Posted in BC-DR, metro cluster, Software Defined, Storage, stretched, stretched cluster, Virtual SAN, VMware, vsan, vSphere | Comments Off on Can I still provision VMs when a vSAN Stretched Cluster site has failed? Part II

Part 2: Is VSA the future of Software Defined Storage? (Customer use case)


Advertise here with BSA

About 6.5 years ago I wrote this blog post around the future of Software-Defined Storage and if the VSA (virtual storage appliance) is the future for it. Last week at VMworld a customer reminded me of this article. Not because they read the article and pointed me back at it, but because they implemented what […] Continue reading

Posted in filter, replication, sds, Software Defined, software defined storage, Storage, vaio, Virtual SAN, VMware Cloud Foundation, vsan, VVols | Comments Off on Part 2: Is VSA the future of Software Defined Storage? (Customer use case)

Joined GigaOm’s David S. Linthicum on a podcast about cloud, HCI and Edge.


Advertise here with BSA

A while ago I had the pleasure to join David S. Linthicum from GigaOm on their Voices in Cloud Podcast. It is a 22 minute podcast where we discuss various VMware efforts in the cloud space, edge computing and of course HCI. You can find the episode here, where they also have the full transcript […] Continue reading

Posted in cloud, edge, hci, Server, Virtual SAN, VMware, VMware Cloud Foundation, vmware cloud on aws, vmware cloud on dell emc, vsan | Comments Off on Joined GigaOm’s David S. Linthicum on a podcast about cloud, HCI and Edge.

Project nanoEDGE aka tiny vSphere/vSAN supported configurations!


Advertise here with BSA

A few weeks ago VMware announced Project nanoEDGE on their blog virtual blocks. I had a whole bunch of questions the following days from customers and partners interested in understanding what it is and what it does. I personally prefer to call project nanoEDGE “a recipe”. In the recipe, it states which configuration would be […] Continue reading

Posted in edge, IoT, robo, Software Defined, Storage, supermicro, Virtual SAN, vsan, vSphere | Comments Off on Project nanoEDGE aka tiny vSphere/vSAN supported configurations!

2 node direct connect vSAN and error “vSphere HA agent on this host could not reach isolation address”


Advertise here with BSA

I’ve had this question over a dozen times now, so I figured I would add a quick pointer to my blog. What is causing the error “vSphere HA agent on this host could not reach isolation address” to pop up on a 2-node direct connect vSAN cluster? The answer is simple, when you have vSAN […] Continue reading

Posted in 2-node, direct connect, ha, isolation response, Server, Software Defined, Storage, Various, Virtual SAN, vsan, vsphere ha | Comments Off on 2 node direct connect vSAN and error “vSphere HA agent on this host could not reach isolation address”