We are hearing about a number of VSAN stretched cluster implementations going on at the moment, which is great news. I just set up such a configuration once again in my lab as we look at some various scenarios for the next release of VSAN. Now, for anyone looking at implementing VSAN stretched cluster, there is the VSAN 6.1 stretched cluster guide which should be your first port of call. However I noticed that once VSAN stretched cluster is implemented, you get a few warnings that you typically wouldn’t see in standard VSAN deployments. That is what I want to…
The storage space has been a very exciting space over recent years. There have been so many new start-ups and new innovations, that it becomes difficult to keep track sometimes. More recently, there has been a lot of news around mergers, acquisitions, shutdowns and IPOs in the storage industry. It got me thinking about a lot of the changes we have seen over the past number of years in the storage market. Just for my own interest, I went back over many of my blogs, and the various conversations I had with people at various VMworld events and VMUG meetings,…
This is something I only learnt about very recently, and something I was unaware of. It seems that we have made a major improvement to the way we do snapshot consolidation in vSphere 6.0. Many of you will be aware of the fact that when they VM is very busy, snapshot consolidation may need to go through multiple iterations before we can successfully complete the consolidation/roll-up operation. In fact, there are situations where the snapshot consolidation operation could even fail if there is too much I/O. What we did previously is used a helper snapshot, and redirected all the new…
In the VSAN Troubleshooting Reference Manual, the following description of VSAN.ClomMaxComponentSizeGB is provided: By default VSAN.ClomMaxComponentSizeGB is set to 255GB. When Virtual SAN stores virtual machine objects, it creates components whose default size does not exceed 255 GB. If you use physical disks that are smaller than 255GB, then you might see errors similar to the following when you try to deploy a virtual machine: There is no more space for virtual disk XX. You might be able to continue this session by freeing disk space on the relevant volume and clicking retry.
With the release of vSphere 6.0 earlier this year, VMware introduced the eagerly anticipated VVols or Virtual Volumes. As we see more and more traction around VVols, a specific question has come up a number of times already. The question is basically: “What happens to VVols if I lose my VASA Provider or my vCenter Server, or indeed both of these components? Will I still have access to my devices?”.
Attention VSAN users. A new Log Insight content pack has just been released specifically for Virtual SAN. For those of you not familiar with Log Insight, this product does automated log management through log analytics, aggregation and search. It allows administrators to analyze terabytes of logs, perform smart parsing to discover structure in unstructured data, and enable interactive, real-time search and analytics through a GUI-based, easy to use interface.
A short post to let you know about some upcoming speaking engagements that I am doing over the next couple of weeks. First up, I will be speaking at the TechUG, or Technology User Group event next week. This event will be held on Thursday, November 26th. It will be held in the Westin Hotel in the heart of Dublin city, Ireland. There is a really good agenda for this event (which is not a VMware centric event), that you can find at this link here. I personally will be speaking about Virtual SAN (VSAN), VMware’s hyper-converged compute and storage…