Cohesity Data Platform 2.0 is out

cohesityCohesity have released their next version (2.0) of the Cohesity Data Platform. I met Cohesity at VMworld 2015, and  I wrote about my first impressions of the solution in a blog post from back in August 2015. In a nutshell, Cohesity are positioning their Data Platform as hyper-converged secondary storage. They want to stop the silo’ing of different storage for backups, file shares and analytics in the data center, and offer you a single platform for all of your secondary storage needs. Now they are ready with the next version, so lets take a quick look at what is coming in this new release.

Continue reading

An overview of the new Virtual SAN 6.2 features

vsan_stretch_graphic_v02_300dpi_01_square140If you were wondering why my blogging has dropped off in recent months, wonder no more. I’ve been fully immersed in the next release of VSAN. Today VMware has just announced the launch of VSAN 6.2, the next version of VMware’s Virtual SAN product. It is almost 2.5 years since we launched the VSAN beta at VMworld 2013, and almost 2 years to the day since we officially GA’ed our first release of VSAN way back in March 2014. A lot has happened since then, with 3 distinct releases in that 2 year period (6.0, 6.1 and now 6.2). For me the product has matured significantly in that 2 year period, with 3,000 customers and lots of added features. VSAN 6.2 is the most significant release we have had since the initial launch.

The following is by no means a comprehensive list of all of the new VSAN 6.2 features, but these are the major features, along with a few other features that I feel might be of interest to readers. In my opinion, we now have a feature complete product, and a world-class hyper-converged solution for any application. Read on to learn about the new features that we have added to this latest and greatest version of Virtual SAN.

Continue reading

Upcoming speaker session at the Singapore VMUG Usercon

singaporeI’m delighted to say that I have been invited to present at the next Singapore VMUG Usercon, which will take place in the Grand Copthorne Waterfront Hotel on Tuesday, March 1st, 2016. I will be using the opportunity to present on Virtual SAN (VSAN) and will be sharing lots of news and information about the upcoming features that we have planned.

It would seem that I am one of the first speakers of the day, so I will have a lot of free time later in the morning and in the afternoon if anyone would like to talk about VMware, VSAN, Virtual Volumes, vSphere Core Storage or anything storage related during the rest of the Usercon.

This will be my first trip back to Singapore in 22 years. I spent a number of months there back in 1994, and I’m curious to see if much has changed. The one thing I do remember are the fabulous hawker markets and food stalls. I’m really looking forward to that.

I’d like to thank the folks at VMUG for making this possible. And I hope to see many of you there. Click here for the Singapore VMUG Usercon registration.

VMUG

Datrium go GA

datriumThis week Datrium announced that their DVX system is now generally available. I met these guys at VMworld 2015, and wrote a closer look at Datrium here. If you want a deeper dive into their solution, please read that post. But in a nutshell, their solution uses a combination of host side flash devices to accelerate read I/O, while at the same time writing to the Datrium hardware storage appliance (called a NetShelf). The NetShelf provides “cheap, durable storage that is easy to manage”. The DVX architecture presents the combined local cache/flash devices and NetShelf as a single shared NFS v3 datastore to your ESXi hosts.

Continue reading

VSAN Stretched Cluster – some possible warnings

vsan_stretch_graphic_v02_300dpi_01_square140We 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 call out here.

Continue reading

Where are they now? Recent changes in the storage space

watnThe 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 and IPOs in the storage industry. It got me thinking about a lot of the changes we have seen over the past 3-4 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, and tried to see where a lot of these companies/products are now, and what they are currently doing. Now, I am not going to mention every single vendor here. I’m simply trying to highlight the ones that were acquired or merged or indeed IPO’ed (and in some cases are no longer with us) during this period.

Continue reading

Snapshot Consolidation changes in vSphere 6.0

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 I/Os to this helper snapshot while we consolidated the original chain. Once the original chain is consolidated, we then did a calculation to see how long it would take to consolidate the helper snapshot. It could be that this helper snapshot has grown considerably during the consolidate operation. If the time to consolidate the helper is within a certain time-frame (12 seconds), we stunned the VM and consolidated the helper snapshot into the base disk. If it was outside the acceptable time-frame, then we repeated the process (new helper snapshot while we consolidated original helper snapshot) until the helper could be committed to the base disk within the acceptable time-frame.

Continue reading