Rubrik 2.0 is out, with a new model and a new service

Rubrik, who exited stealth only a few months ago, and launched their r300 series of converged data management appliance, have just announced version 2.0. You can read up of the Rubrik launch here. The 2.0 version has a new service called “Unlimited Replication” and a new appliance to the r300 series, the r348 “Hybrid Cloud Appliance”. Rubrik co-founder and CEO, Bipul Sinha, stated in the press release that Rubrik continues to transform “how companies approach data protection and recovery at scale”.

vROps Management Pack for Storage Devices 6.0.2 is GA

Today sees the release of the vRealize Operations Management Pack for Storage Devices (MPSD) version 6.0.2. This is exciting for me as it means that vROps now has management and monitoring features for Virtual SAN 6.0.  The management pack comes with a set of default dashboards for Virtual SAN clusters, as well as the ability to monitor and create proactive alerts/notifications based on VSAN events. I took the vROps Management Pack for a spin a little while back, and used it on my own lab cluster. Included below are a few of the features that it has.

Handling VSAN trace files when ESXi boots from a flash device

I’ve been involved in a few conversations recently regarding how VSAN trace files are handled when the ESXi host that is participating in a VSAN cluster boots from a flash device. I already did a post about some of these considerations in the past, but focused mostly on USB/SD. However SATADOM was not included in this discussion, as we did not initially support SATADOM in VSAN 5.5, and only announced SATADOM support for VSAN 6.0. It seems that there are some different behaviors that need to be taken into account between the various flash boot devices, which is why I…

New storage vendors to check out at #VMworld 2015 (SFO)

As usual, there have been loads of things happening over the last 12 months in the storage space. The Solutions Exchange at VMworld is always a great place to meet new storage startups, and get some further information on their respective products and innovations. This year, I’ve made a note of a few startups that I wish to catch up with at VMworld 2015 and find out what issues are they trying to address with their technology, and why should a customer choose  their solution over some of the others in the storage space. Disclaimer: Please note that I am…

Is VSAN for you? It’s never been easier to check…

A common question we receive when we meet with customers and talk about Virtual SAN is “whether or not VSAN is going to be able to run my particular workloads?” This is a great question to ask, as most customers are coming from a background of SAN or NAS storage arrays, fibre channel, FC switches, HBAs, CNAs, etc. Since VSAN is still relative new (18 months old at this point), being confident that this new product can successfully run existing virtual machines and applications is paramount. To that end, VMware has developed a number of tools that are simple to…

Announcing Virtual SAN Health Check Plugin 6.0 Patch 1

Announcing some important news for VSAN 6.0 users, especially those using the VSAN Health Check Plugin. If you are using the Virtual SAN Health Check Plugin version 6.0 (and if you use Virtual SAN 6.0, you definitely should be using it), there is a new patch now available. Note that this new Health Check plugin version 6.0.1 release only requires the vCenter server to be updated. There are no new ESXi host side VIBs required. The patch comes as a new installable RPM for the vCenter appliance and a new MSI for Windows versions of vCenter server. [Update] For the…

Heads Up! Misbehaving APD functionality in vSphere 6.0

A very quick “public service announcement” post this morning folks, simply to bring your attention to a new knowledge base article that our support team have published. The issue relates to APD (All Paths Down) which is a condition that can occur when a storage device is removed from an ESXi host in an uncontrolled manner. The issue only affects ESXi 6.0. The bottom line is that even though the paths to the device recover and the device is online, the APD timeout continues to count down and expire, and as a result, the device is placed in APD timeout…