Author Archives: Brandon Willmott

About Brandon Willmott

Brandon Willmott is a Global Sr. Solutions Engineer at VMware, 7x VMware vExpert, founder of the New Orleans VMUG and founder of the Baton Rouge VMUG. Brandon has been in IT for over 15 years, and holds VCP and CCNA certifications.

Where’s My VMware Cloud Foundation License?

A common question I receive from customers is why they don’t see a VMware Cloud Foundation license in the MyVMware portal. What appears instead is licenses for each individual product that make up the VCF edition you purchased. Which is typically:

  • vSphere & vCenter
  • vSAN
  • NSX
  • SDDC Manager
  • vRealize Operations, Automation, and Log Insight
  • Horizon (optional)
  • Enterprise PKS (optional)

So how do you consume these licenses? Assuming you have the hardware in place and you’re ready to bring up VCF, the first step is to deploy Cloud Builder and download/complete the VCF deployment parameters worksheet. In the deployment parameter worksheet, you’ll enter license keys for the following components:

  • vSphere & vCenter
  • vSAN
  • NSX
  • vRealize Log Insight

The license keys should match with the version of VCF that you’re deploying. During bring-up, the license key audit only validates the format of the key, not the accuracy. See the Bill of Materials (BOM) in the VMware Cloud Foundation Release Notes for the specific product versions supported in each release.

With the management workload domain deployed, you’ll (optionally) enter the license keys for:

  • vRealize Automation; you can also use a vRealize Suite or vCloud Suite license key
  • vRealize Operations; you can also use a vRealize Suite or vCloud Suite license key
  • vRealize Log Insight
  • NSX-T
  • Horizon

To get started, select Licensing from the left navbar:

Which brings up the existing licenses that have been added (in the example below, I have a fully deployed SDDC):

Click the + LICENSE KEY and add each product key:

Now that licenses are added, you can create a new workload domain, add a host to a cluster, or add a cluster to a workload domain.

Tracking Performance and Usability Enhancements to VMware vSAN Since 6.6.1

I’ve been at VMware for 12 weeks now and continuing to work towards being a vSAN expert. One of my many challenges facing that goal is not only learning the current state of vSAN’s features and capabilities (the latest being 6.7U3) but also learning how vSAN operated in previous versions to articulate to my customers why feature X in this release is relevant to them.

VMware has released updates to vSAN 75 times since the initial release in 2014 and 12 updates in 2019 alone. So where is the best place to start for having a foundational understanding of modern vSAN functionality? VMware called version 6.6 their “Biggest Release Ever” back in 2017 and admittedly, while at Pure Storage, that’s the version that I started to recognize that vSAN had matured a lot so this version would be the basis for level setting my knowledge on what most customers’ experience with vSAN will be. However, of the handful of customers that I support in my Global Accounts role at VMware, most are running at least vSphere 6.5U3 so vSAN 6.6.1 will be the basis for my learning.

One of the confusions I’m adjusting to diving into vSAN is that vSphere and vSAN versions don’t match. One would reasonably expect a product built into another one to have matching versions but they rarely do. Interestingly, they have matched in the past! One of the most helpful documents I’ve used at VMware while ramping up is KB 2150753, Build numbers and versions of VMware vSAN. I’ve referenced this KB article many times to correlate vSphere and vSAN versions. At the end of the day, matching version numbers is a nice to have “feature” but not matching is the reality of two separate business units working on their own products with specific goals and milestones to reach different major and minor releases.

I’m going to highlight major performance and usability enhancements to vSAN in the past 4 release:

What Was New in vSAN 6.6.1

A typical minor dot-release for vSAN: a few new enhancements but nothing major. Although there were 12 updates to 6.6.1 since it’s initial release (Express Patches, Patches, and Updates), I couldn’t find any release notes. Fundamentally, these were the most important features in this release:

  • VUM Integration: VUM integration automates the process of ensuring that hardware installed in the cluster is on the VMware Compatibility Guide (or HCL). It also provided firmware updates for select hardware vendors such as Dell, Lenovo, Supermicro, and Fujitsu. A known issue in this release is that Custom ISOs are not supported in vSAN build recommendations and hosts built on custom ISOs will display as Non-Compliant.
  • Storage Device Serviceability (Blink Disk Lights): When a device fails, it’s extremely important to be able to find it in the server! This feature gives you the ability to select the disk in the UI and make the LED light blink. Great feature but in this release, it’s limited to HPE DL/ML series servers with Gen 9 controllers.

What Was New in vSAN 6.7 GA

A big usability enhancement in this release was the HTML 5 Client becoming the standard interface for vSphere! Other notable performance enhancements included:

Adaptive Resync

Source: StorageHub

This feature includes three main components: congestion control mechanisms, a dispatch/fairness scheduler, and a bandwidth regulator. In essence, under contention vSAN has the ability to throttle I/O caused by resync operations in favor of prioritizing VM I/O. Before this feature was added, VM I/O was in an every-man-for-himself battle that could cause performance. The adaptive nature of this feature means it’s always on and allows it to be an invisible vSAN operations that doesn’t need any user-defined capabilities. The Adaptive Resync Deep Dive on StorageHub goes into much greater detail.

New Health Checks in vSAN Health

vSAN Health is a cloud-connected, built in framework for providing proactive health checks for vSAN clusters. Participation in VMware’s Customer Experience Improvement Program (CEIP) is mandatory to realize this benefit. This capability was initially released in vSAN 6.6 and additional checks were added in 6.7 included:

  • Host maintenance mode verification
  • Host consistency settings for advanced settings
  • Improved vSAN and vMotion network connectivity checks
  • Improved vSAN Health Service installation check
  • Physical Disk Health checks combine multiple checks into a single health check
  • Improved HCL check
  • Firmware checks are now independent of driver checks

Pete Koehler, in VMware’s HCIBU technical marketing group, wrote a detailed post on the health checks as well as a video: #StorageMinute: vSAN Health Checks – Guidance and Remediation Made Easy.

Stretched Cluster Enhancements

This release had 3 new features to improve performance and relaiability when using stretched clusters. Namely:

  • Intelligent site continuity: If there’s a partition in the cluster (link goes down, etc), vSAN will first validate which site provides maximum data availability before establishing a quorum with the witness. For example, if Site A (preferred) lost a node or a device during the partition and objects are in a degraded state but Site B (secondary) is healthy, vSAN will consider Site B active until Site A is healthy again.
  • Witness traffic separation: A separate vmkernel NIC can be dedicated for vSAN witness traffic when using stretched clusters. Previously it was required for the data network to communicate with the vSAN witness host and that VLAN to be stretched across the WAN as well. When deploying stretched clusters, separating witness traffic is recommended.
  • Efficient inter-site resync: A proxy host is established for components that need to be resynced across sites following a failure instead of copying the objects across the WAN to meet the storage policy requirements
Inter-site resync enhancement in vSAN 6.7 GA

More details on vSAN 6.7 GA updates can be found in the release notes.

What Was New in vSAN 6.7 Update 1

vSAN 6.7U1 seems it was the biggest update to vSAN since 6.6 and there’s a lot of great performance and usability enhancements in this release!

Cluster Quickstart

Cluster Quickstart Wizard enables new vSAN and non-vSAN clusters to be created quickly via the vSphere client or APIs.

Cluster Quickstart Wizard in vSphere 6.7 Update 1

The following tasks are performed to speed up and ease the deployment process of vSphere clusters:

  • Setup HA, DRS, and vSAN
  • Add hosts
  • Select vSAN deployment type
  • Network configuration including vSphere Distributed Switching
  • Disk Group configuration
  • Enable Deduplication & Compression / Encryption

VUM Updates

Remember how in 6.6.1 there was VUM integration? Well kinda…what was missing was the ability to utilize VUM to update vSAN clusters when using OEM-specific ISOs. That’s fixed in this release but still no ability to update vSAN through VUM with custom ISOs.

Maintenance Mode & Host Decommissioning Enhancements

When entering a host into maintenance mode whether to perform updates or simply decommission it, vSAN will now perform a full simulation of the activity (assess the capacity/availability impact of host going into maintenance mode and ability for cluster to redistribute object components) and report back success or failure.

Additionally, the “object repair delay timer” setting (around since vSAN 5.5) is now in the GUI. This allows an administration to modify the amount of time to wait for vSAN to rebuild data when components are out of compliance with the storage policy due to a disk or node failure.


vSAN now has awareness of TRIM/UNMAP commands sent from the Guest OS and can reclaim previously allocated blocks as free space.

Mixed MTU Support for 2 Node and Stretched Clusters

Remember that Witness Traffic Separation (WTS) feature in 6.7 GA? It was nice that a different vmkernel port could be used to separate vSAN data traffic from witness traffic; however, it was still required that the MTU matched on all vmkernel interfaces. That changed in 6.7U1 and now it’s possible to have Jumbo Frames on the vSAN data vmkernel interfaces while using a standard MTU setting on the vmkernel interface for witness traffic!

Enhanced Health Checks & Support

  • Network performance health check ensures that sufficient performance can be achieved
  • Display and classify multiple, VCG-approved storage controller firmware versions such as not latest, latest, and not on HCL
  • Expanded diagnostics in vSAN Support Insight which give GSS tools to capture network diagnostic data and further reduce the need for collecting and transmitting logs
Enhanced diagnostics for GSS in vSAN Insight

More details on vSAN 6.7 Update 1 features can be found in the release notes.

What’s New in vSAN 6.7 Update 3

Finally! We’ve made it to the current version of vSAN and you may have noticed that we skipped over Update 2. That’s because vSphere 6.7 Update 2 didn’t include any new features or enhancements to vSAN so it was skipped. I guess VMware tries to keep versions aligned after all?

Update 3 is another huge leap forward for vSAN with the biggest being the introduction of Cloud Native Storage. This isn’t specifically tied to just vSAN. Instead, it enables vSphere to provide persistent storage to Kubernetes and gives the vSphere administrator the ability to select the required storage (vSAN, VMFS, NFS) for the pod. There’s an excellent doc on Getting Started with VMware Cloud Native Storage here which walks you through setting up a k8s cluster, deploying applications, and managing container volumes.

  • VUM integration gets another update: instead of showing only the latest version of vSAN, you can create new baselines to stay that allow you to stay at the current version and only show new patches and updates
  • New Monitoring and Dashboards
    • Capacity Monitoring Dashboard has been redesigned to provide better visibility into overall as well as granular utilization. New insights per site, per fault domain, and host/disk level
    • Resync: improved accuracy when displaying time remaining to complete a resync
    • Data migration pre-check: new dashboard that provides detailed information when performing data migration activities for maintenance mode tasks. Provides insight into object compliance, cluster capacity, and even predicts the health of the cluster before placing a host into maintenance mode

Parallel Resynchronization

In the past, when vSAN was resyncing components, it would use a single thread to copy the data. This isn’t really a problem if the components are small as they’re likely to transfer quickly; however, what if we have many max-size components (255GB) due to large VMDKs? For example, a 5TB VMDK will span over 20x 255GB components. In vSAN 6.7U3, it will now leverage numerous parallel streams per component to make resyncs complete faster. Bandwidth for this process is managed by Adaptive Resync that was introduced in 6.7 GA.

Introducing Automatic Rebalance

In previous versions of vSAN, administrators could manually initiate a proactive rebalance after being alerted by a vSAN health check that disk(s) were imbalanced. Now automatic rebalancing can be configured to enable vSAN to handle these operations without user intervention. Information on how to enable automatic rebalancing can be found here. Be sure to adjust the vSAN health check to prevent unnecessary alerts!

New Tool: vsantop

vSphere administrators have been using esxtop for years and now there’s a similar tool, vsantop, to measure CPU usage for storage-related tasks to help with troubleshooting and support cases. This can be especially useful to provide quantifiable measurements to assist administrators understanding the impact of using data services like dedupe & compression or data at rest encryption.

There is still significant enhancements that improved I/O handling, resync and rebalancing performance, and degraded device handling since vSAN 6.6.1 that weren’t mentioned here. VMware has made significant investments in vSAN since it’s release in 2014 and serves as a solid foundation for on-premises and hybrid cloud storage.

This exercise was very productive to help me understand the progress that vSAN has seen over the last 2 years and has better prepared me to discuss upgrade paths and new features with customers.

Level Up at the next VMUG Virtual Professional Development Event

Let’s be honest — if you’re a VMUG member, you get quite a few emails from VMUG and probably delete them without looking or quickly scan it and then delete it. I tend to do the latter but the one I received this morning caught my attention and quickly turned to excitement and I wanted to do my part to promote what I’m expecting to be a very beneficial event.

Lately I’ve spent a lot of after hours time working on my own professional development and specifically focusing on leadership as I feel that my future roles in technology will require that skill. But it’s also an important skill in my role as father raising 3 children.

The upcoming VMUG virtual event’s keynote speaker will be VMware CEO, Pat Gelsinger, where he will share his “Five L’s of Leadership.” The event will also include 5 members of the VMUG community that will share their experience ranging from broad topics such as resume writing, networking, and public speaking as well as deeper topics to help you identify your brand and use it for your future success.  I’m looking forward to hearing each of the following speakers:

  • A Public Speakers Guide to Public Speaking, Chris McCain, Director of Technical Certifications @ VMware
  • Soft Skills, Resume Building and Networking are Some of the Toughest Areas to Master, Paul Nadeau, Sr. SD-WAN Systems Engineer @ VMware
  • Tips and Habits to Advance Your IT Career, Ariel Sanchez, Sr. Technical Account Manager @ VMware
  • Growing From VI Admin to SRE, Michael Roy, Product Line Marketing Manager @ VMware
  • Achieving Happiness: Building Your Brand and Your Career, Amanda Blevins, Sr. Director & Chief Technologist @ VMware

Over my 15 year career in IT, all of these skills have been extremely important to plot a course, go on a journey, and execute on those goals. The two latest journeys I’m taking are public speaking and building my brand. I’ve been fortunate to have found the VMware community through social media nearly 10 years ago and found industry experts to follow and learn from but I’m making an concerted effort now to raise my voice and share my ideas. 

I hope you’ll join me along the way. To join the VMUG virtual event on September 19 from 9 AM – 3 PM, register here: Let your voice be heard too! Share what you learned at the event on social media and your plan to sharpen your skills.

VVols Readiness Checker for Pure Storage FlashArray

The SE organization at Pure has been hard at work promoting VMware VVols as it enables customers to take the next step in their virtualization journey: mobility. In an earlier post on the Pure Storage blog, Ray Mar wrote about the simplest VVols implementation in the industry. Getting up and running with VVols is effortless but there’s always those pesky minimum requirements to know about before you can begin implementing VVols.

While reviewing the VVols Quick Start Guide, there were quite a few things to be mindful of:

  • Minimum vSphere version
  • Minimum Purity version
  • NTP servers configured on ESXi, vCenter, and FlashArray
  • FlashArray management ports accessible on port 8084
  • Host and host groups are present on the FlashArray
  • If replicating, make sure all of these requirements are met on the remote side too!

As the sharp system admin you are, you can probably take a quick glance at the requirements and know you’re good to go. But, it’s a great idea to double check a setting such as NTP that is usually “set it and forget it.” On a small cluster it’s easy enough to click around on a few hosts and vCenter and make sure it’s set and turned on but that’s no bueno on a much larger cluster. Sounds like a great task to be automated! With that in mind, I created the VVols Readiness Checker to quickly validate these prerequisites with PowerShell using PowerCLI and the Pure Storage SDK.

The script can be run on your local machine or server and will download PowerCLI and the Pure Storage SDK if it’s not present. After entering your vCenter, FlashArray, and associated credentials you’ll quickly get a summary of your environment’s readiness to implement VVols.

Sample ESXi host summary
Sample FlashArray summary

Once you’re finished addressing any warnings, proceed with the Quick Start Guide to update the vSphere Web Client plugin, register the VASA provider, and create the VVols Datastore!

I highly recommend importing the FlashArray protection groups as VM storage policies as this gives you fine grain control and validation via compliance checks that ensures the VMs are always protected as required by the business.

Example FlashArray Protection Groups as VM Storage Policies

Be sure to check out Cody Hosterman’s VVol’s landing page for even more VVols details!

Update: Veeam Support for Volume Snapshots of a FlashArray Protection Group

In a previous post, I wrote about taking FlashArray snapshots with Veeam using a PowerShell script. At the time, there was a limitation that prevented Veeam from seeing protection group snapshots. The Pure Storage Plugin for Veeam version 1.1.40, was released on August 24, 2018 and support for volume snapshots created as part of a Pure Storage Protection Group are now available. Check out the KB article to download the update. Installation is a simple wizard that takes a minute or so to install.

No settings need to be changed on FlashArray or Veeam to see Protection Group snapshots. When selecting a volume on FlashArray, you can see snapshots from a protection group (highlighted) and those taken separately by Veeam as part of another protection policy.


With multiple options for snapshot policies, what’s my recommendation for a best practice? Continue to leverage the volume or protection group snapshot policies on FlashArray. Veeam has visibility into volumes on the FlashArray but can’t manage Protection Groups. Having the ability to group volumes on FlashArray to snapshot and replicate and maintain one retention schedule is easier to administer.

What I would like to see in the next iteration of the plugin is the ability for Veeam to truly integrate with protection groups (consistency groups on other arrays). It looks like Veeam’s Universal Storage API for Integrated Systems will need additional functionality though. The API’s documentation doesn’t describe that functionality.

Taking FlashArray Snapshots with Veeam

In April 2018, Veeam released the Universal Storage API which enabled storage vendors like Pure Storage to create integrations for Veeam with their storage system. At a high level, this functionality allows Veeam to leverage storage system snapshots when performing backups as well as take snapshots of volumes for instant restore of VMs or granular file restoration.

In the initial release of the Pure Storage FlashArray plugin, the ability for Veeam to see and utilize existing snapshots on the FlashArray is unavailable. Additionally, it’s not currently possible for Veeam to take snapshots of all the volumes associated with a Protection Group. Joint customers have expressed the desire for this functionality but development takes time.

In the mean time, I created a script that gives customers the ability for Veeam to create snapshots of all the volumes in a FlashArray Protection Group. This script is designed to be run automatically using Windows Task Scheduler; however, you can run it from a PowerShell command prompt for a quick, one time use.

The most significant use case I created this for was recovering file shares faster if it was encrypted by a malware attack. It’s totally possible to immediately remediate the most extreme case where the whole file share is encrypted by overwriting the volume from a storage snapshot but what if it’s just a user’s home directory or a small subset of the file share?

In the following example, I have snapshots on the FlashArray that were taken by Veeam:


From Veeam’s view:


When selecting a snapshot, you can see each VM protected by that snapshot:

This integration is extremely powerful as it provides instant VM, guest file, and application item recovery from FlashArray snapshots instead of backup.

In a sample test, I recovered a single Windows Server 2016 VM in just over a minute:


Veeam performs this operation similar to how it operates when restoring from a backup, with the exception that it creates a volume on the FlashArray from the snapshot,  presents it to the applicable host, rescans the hosts’s HBA, mounts the volume, and adds the VM to vCenter.


Known Limitations

Currently the first version of this script only supports volume-based Protection Groups. If your Protection Group’s members are hosts or host groups, the script will not work. I anticipate fixing this in an upcoming release as well as adding the ability to specify a volume instead of a Protection Group. Additionally, this script doesn’t limit the number of snapshots taken so please monitor your usage. A future version will address this issue as well.

If you have questions about installing and configuring the Pure Storage FlashArray plugin for Veeam, check out Stephen Owens’ blog posts:


To download the script, head over to the script’s repository on my GitHub page.

Taking My Talents to the Docker Community

After reflecting on my personal goals and the recent announcement that VMUG was joining the Dell Technologies User Community, I’ve decided to step down from the leadership role of the New Orleans VMUG effective immediately and focus my attention on building the Docker community in Louisiana. This hasn’t been a rash decision because of the “acquisition” of VMUG by DTUC but rather an affirming indicator that now is the right time to move on.

I’ve been part of VMUG leadership since 2010 when I started the Baton Rouge VMUG (and sequentially the New Orleans VMUG in 2011). My motivation to start the groups stemmed from my lack of knowledge about virtualization, the desire to learn what others are doing, and what new technologies were coming to the market. I didn’t want to just be a consumer though, I wanted to create an environment where I could learn and then help others who had the questions of their own and start a feedback loop. After 6 years, I can look back and say that I was successful in achieving those goals and now I’m looking for the next challenge.

Why Docker and why now?

I’ve been following Docker since 2014 and have watched the project mature and continue to gain in popularity. In 3 short years it has become the de facto standard for building cloud native applications and a robust ecosystem is forming around it much like with VMware a decade ago. The technology is still in it’s infancy and the population of IT professionals don’t know about it but the number of early adopters continues to rise and drive further development and innovation at a rapid pace. Now is the perfect time to get in at the ground floor and begin building a community.

As an open source project, community is at the heart of what has fueled Docker’s growth. Forty one percent of Docker’s contributors are individuals! That speaks volumes for the commitment that thousands of people around the world have made to improving a project. At it’s core, Docker, Inc. embraces community and local groups have exploded in popularity. As of May 2017, there are 288 groups around the world. I encourage you to take a look at the list of Docker meetup groups and get involved. There’s even an online meetup if you can’t attend one locally.

This is also an exciting opportunity for me to grow as an IT professional and network with a different group of professionals. I’ve been an amateur developer since 8th grade but knew it wasn’t a career path for me but as infrastructure has become more “cloud”-like, my interests have shifted to trying to learn more about applications and how they’re deployed. What platforms are used? What barriers exist to reliably getting stable code into production? What day-to-day challenges do developers face? I look forward to the opportunity to personally grow and being a part of the Docker community will allow that as it is currently geared more towards developers. However, the technology is becoming mainstream and the necessity to enable ops teams to successfully manage containers will be more important. It will undoubtedly lead to an even larger ecosystem and participation by former virtualization engineers as their organizations restructure their environments.

What’s your take on VMUG becoming part of the Dell Technology User Community (DTUC)?

First and foremost, my decision has nothing to do with disliking Dell EMC nor do I have a lot of commentary on what this means for the future of VMUG. My dissatisfaction lies with how the VMUG CEO, President, and Board handled this very important decision that aligns a previously independent community with a corporate run community. I strongly disagree with this path for VMUG and I don’t feel that Dell EMC brings value to a community that has been successfully grown and managed through grassroots efforts. VMUG HQ has greatly veered away from their original objective of supporting leaders to build a successful community for VMware customers. I know my fellow leaders will defend their ability to bring in sponsors and topics that are in the best interest of their local community regardless of the alignment with Dell EMC. I’m uncertain what the future holds for VMUG but I know that communities will stick together no matter what obstacles are presented.

I’m Going to OSCON!

I’m very excited that I’m attending my first OSCON this year, compliments of The Cloudcast. On the April 25, 2016 episode, it was announced that they were giving away two Bronze Level passes to the conference. To win a pass, they asked to send in a personal story about community and why you wanted to attend OSCON. I wanted to share my story with a wider audience:

I’ve had an interest in Linux and coding since 6th grade and did some intermediate level coding in high school, college, and in my career. Finding help online to complete a coding project or successfully getting something like XWindows running in the late 90s was quite difficult. Similarly today, learning new, uncharted, and complex systems such as Kubernetes and Mesos is challenging but the community around it is fanatical and extremely helpful. I find that the community surrounding a technology is a key to it’s success and the success of the business. I’ve found myself gravitating to upcoming technologies that have deeply rooted and committed communities because those are the ones that usually become a mainstay in the industry.

One of my first experiences with such a community was the VMware community via Twitter in 2010. I started down the path of virtualization at my employer and my head was spinning. I happened to find that there was a vast community of virtualization evangelists that shared best practices and experiences and it was awesome to connect with hundreds of people who were there to help others. From there, I learned about local VMware user groups and wanted to participate in one to hear what others were doing and try to learn more. Living in Louisiana, which isn’t a major city/tech hub, there wasn’t a local group. I found tremendous value in the virtual community and I wanted the same experience of learning and sharing in person as well. I reached out to VMware and told them I wanted to start a local chapter of the VMUG. I started the first VMUG in Louisiana in Baton Rouge and a year later, due to it’s success, VMware asked me to form and run a second user group in New Orleans. I’ve been running the New Orleans group for the last 4 years and continue to enjoy learning about how organization’s environments are maturing with the maturation of the ecosystem.

As virtualization has solidified itself as a basic function of the datacenter, I’ve found myself following the maturation of the datacenter and it’s all pointing towards open source software. This has been very refreshing for me personally because it feels that there has been a reset in the datacenter as it begins to reinvent itself. Once virtualization became an anchor of the datacenter, VMware and other ecosystem partners moved up the stack to build upon that foundation. This has brought more end-user related products to the market but has left the infrastructure architect without many new tools with which to innovate. Containers will be a pillar of the next generation datacenter and it’s all fueled by open source software. I’m excited to see how the shift away from enterprise software vendors, which have been to  have rigid and archaic ways of designing software, changes over the next few years. The flexibility of OSS will give organizations a way to consume software through the community which is free and empowered to define how the software or application is best built. The community around these technologies will have a strong influence to guide it in the best direction but the biggest impact of the community is to be engaging with each other to guide newcomers and strengthen the established members.

I look forward to becoming part of this community and meeting new people next week.

9 Months at PernixData: Recapping My Best Career Decision

It’s hard to believe that my one year anniversary at PernixData is in 3 months. I have to say that coming here has been the best career decision I’ve ever made. I’m proud to be a part of the fastest growing software infrastructure company in history and surrounded by highly talented and passionate people. Having come from the customer side, specifically a medical practice, it’s interesting to be part of a software company and be a part of a startup.

PernixData is now a 3 year old company and I previously didn’t think I would ever join a startup. When I considered other opportunities at other young companies in the past, my family always cautioned me on having stability. I stayed at a 30 year old company for 10 years in the name of comfort and stability and I have some regrets about it. Louisiana isn’t busting at the seams with jobs in enterprise IT so the associated risk of joining a startup and losing my job one day weighed heavily on me. The security of an established organization was very comforting but I recognized that my growth was extremely limited due to the size of the organization and their plans for growth. Building the proverbial IT mansion was fun because I left the organization with a solid infrastructure but after the projects were over, the upkeep was minimal and the days became mundane. The decision to move on came down to fulfilling a desire to grow professionally by facing a new challenge outside of out of my comfort zone.

When going to a startup there can be a lot of risk and a lot of reward. Aside from believing in the architecture, what gave me comfort in joining a young company is it’s leaders. Satyam Vaghani and Poojan Kumar aren’t household names but they were both seasoned VMware alum that had a vision and brought along a team of world class developers that could execute that vision.

There’s risk with everything in life, but I opted to set aside my overly cautious feelings about job security and jumped right in because I only see PernixData continuing to grow.

The transition from Director of IT to Systems Engineer was exactly the change I was looking for because I was burnt out with operations. The career change also gave me the opportunity to explore existing, new, and upcoming technologies and understand how they relate to FVP. In my previous role, my experience with various hardware and software configurations were limited because there I felt learning about them wasn’t beneficial because they weren’t relevant to my job nor would we ever need to implement a solution like it. (Note: I recognize this was a terrible mindset to have and have since changed.)

As the Director of IT of a small company, I was responsible for maintaining the infrastructure and I was the manager of a desktop tech. The desktop guy was great at his job but I didn’t have a peer to collaborate with. That’s why starting a VMUG in Louisiana was important to me — I wanted a community of peers to share and learn with about virtualization.

The PernixData SE team is a great example of the peer community that I wanted to be part of. I’m surrounded by around 20 other engineers that have come from various backgrounds such as a fellow IT Director, virtualization admins, VMware instructor, and experienced SEs. Each of us has worked in different verticals and with different applications, hardware, and end users. This diversity allows each of us to bring our unique experiences and contribute them to the team and further develop a highly skilled and technical team. I’m also very proud that over 90% of our team are VMware vExperts.

What has been the most fun about working at PernixData is meeting people across the country and challenging them to re-think how they purchase storage and drive application performance. During the POC process, I love talking about technology with customers, learning about each company’s environments and challenges, and ultimately letting FVP speak for itself. In my opinion, being able to stand behind the product that you sell is ultimately what removes some of the challenges of being in sales and makes it enjoyable.

If you work for PernixData at HQ, there’s a lot of perks but as a remote employee I don’t benefit from but working at home is a great supplement. I don’t know how I could ever go back to working in an office, that’s for sure! Personally, the transition from office worker to teleworker hasn’t been difficult because I talk to quite a few customers everyday and always staying in touch with team members.

On a personal note, my wife is almost always home because she works at night as a registered nurse. For some, working from home while their spouse is there has presented challenges. This hasn’t been the case for us but YMMV! Another perk that I enjoy about working from home is being to take my kids to school occasionally and always being here when they get home from school. Once they’re home, they love to come into my office and keep me company for the rest of the day. It’s not always unicorns and rainbows though, I have to kick them out quite a bit!

Overall, I’m very pleased with how the last 9 months have turned out and always looking forward to the next day.

Shiny new vStuff — Speak at a VMUG NOW!

Having spent the last 3.5 years as a VMUG leader of two different VMUGs and spent time talking to over a dozen other leaders, one issue persists in the VMUG community: lack of customer participation. VMUG recognized this and implemented the Feed4ward program to, “encourage every interested member to share their knowledge at a VMUG local group meeting or User Conference”. Knowledge sharing is what everyone’s there for but most of the time people are nervous about public speaking, don’t think they know enough to discuss topics with others, or they think what they do isn’t that different or interesting. That can all changes now! 

With the release of vSphere 6 on March 12, everything is new to everyone. Not many people have downloaded it in their test/dev/lab environment and (hopefully) no one has deployed it in production yet! There are 11 vSphere ecosystem products that got updated and probably thousands of new features or enhancements to discuss. If you think just an “upgrading to ESXi 6” presentation will be boring, look at upgrading or starting to use one of the other supporting vSphere products such as vRealize Automation or Operations Manager. Maybe you’re a SMB and using or looking to use vSphere Data Protection or vSphere Replication. What was the upgrade or setup process like? How do you manage it? Did you ever have to recover from a backup or replica? Any gotchas? There’s plenty of opportunity now to get started giving back to your local VMUG community. If you want mentoring, look into the VMUG Feed4ward program!

The vSphere 6 documentation ca be found at:

Take this time to get out in front and start getting familiar with the new features and the associated documentation. Many organizations will look to upgrade once update 1 rolls around (I was in this crowd) which will probably be released in 6 months. Take the lead, become the expert, and be a staple in your local community.

The local VMUG leaders will probably already have a “What’s new in vSphere 6” slot carved out at the next meeting but if there’s a product feature or enhancement you like, love, or have always wanted to see, speak with them about adding a deep dive into that topic. It’s highly unlikely they’ll say no!