An interesting issue came in from one of our customers that they were unable to provision a new vVol Disk on a VM that was based on a VMFS Datastore. After some troubleshooting it seems there was a regression which no longer makes this available in the UI. Take a look at this blog post on how I will cover a workaround.
In May 2020 Pure Storage released the latest version of their plugin version 4.3.1! This post will explore what’s new in this release!
On April 2, 2020 Pure Storage released the latest version of their plugin version 4.3.0! This post will explore the latest features in this release!
Beginning with version 4.2.0 the Pure Storage vSphere Client Plugin had a whole slew of new features added, one of those features was the ability to integrate authentication with Pure1 allowing fleet registration of all your Pure Storage Arrays among other things. This does require a slight change on how you would normally register your arrays in the plugin, so lets take a look at how we can accomplish this!
Welcome back! If you followed my previous post on Installing and Updating the Pure Storage vSphere Plugin, you may be wondering well What’s Next? Now its time to use it, which will empower your VMware Administrators to be awesome Pure Storage Administrators without ever needing to login to the Pure Storage UI!
Welcome to the first of many Pure Storage blogs. As I get ramped up with the latest information I plan to do a series of getting started with Pure Storage features. These blogs will cover things such as the vSphere Client (HTML5) Plugin, FlashArray, FlashBlade and integrations with other VMware products. First up is learning to install and update the Pure Storage vSphere Client Plugin.
Now that we have covered the considerations to backup each component in your vSphere Environment, it’s time to think about the rollback or restore process. In the previous post we discussed how to backup each individual component, in this post we will continue the conversation and discuss considerations to restore or rollback your vSphere Environment components. Platform Services Controller / vCenter Server When things don’t go right with an update, upgrade or configuration change of your Platform Services Controller or vCenter Server you need to understand the proper steps it takes to rollback.
You spend time planning and implementing updates, upgrades and configuration changes to vSphere Environments. Rollback or recovery is usually the last thing on the mind. Did you know there are multiple ways to successfully backup each component in a vSphere Environment? There are also many ways to recover those same components. In this series we will talk about considerations to backup and restore or rollback your vSphere environment if we have a need to.
Windows Server 2008 and 2008 R2 will be end-of-life on January 14th, 2020. This impacts quite a few folks who may have deployed their vCenter Server for Windows on these Operating Systems. I have been asked quite often recently, “What are my options?” Let’s dive in and find out what it takes to move to a supported OS!
vSphere 6.5 first introduced vCenter HA and since its inception has been deployed in many environments. When it comes to upgrading or updating your vCenter HA environment there are some specific considerations. If you have wondered what it takes to handle the lifecycle of a vCenter HA enabled vCenter Server, keep reading! vCenter HA Overview vCenter HA has seen wide adoption as customers wish to provide provide high availability for their vCenter Server.