Last week I had an attempt at the vSAN Specialist exam (5V0-21.19) and I’m happy to say I passed. This was also my first exam done with the Pearson VUE remote proctoring option so I’ve written a few points on that as well
In a previous post I described how we are setting up remote offices for a customer with two-node vSAN clusters. I meant to get this post out right after that previous one, but things happened… Anyways, here’s how we automated those two-node vSAN clusters.
Currently we have 7 of these racks ready with more to come. As these will be installed at distant locations we are extra keen on knowing that they are all configured as they should, and that the configuration is the same cross these multiple locations.
Recently we received lots of new hardware destined for a customer that has multiple locations world-wide.
They need a robust server solution for their production environments locally. The environment is small in terms of number of VMs, but there is high demands on the environment and we need local hardware at the sites as the connections to these sites varies and they are not fast enough at all times.
Lots of racks
In my blog series on building a solution for monitoring vSphere Performance we have scripts for pulling VM and Host performance. I did some changes to those recently, mainly by adding some more metrics for instance for VDI hosts.
This post will be about how we included our VSAN environments to the performance monitoring. This has gotten a great deal easier after the Get-VSANStat cmdlet came along in recent versions of PowerCLI.