One of the things that regularly pops up in our health checks in VMware environments are connected CD Drives that prevent DRS from functioning properly or prevents a host from entering maintenance mode when doing thing like patching.
In large environments it can get very tedious to disconnect all those drives manually. With PowerCLI it is just one line.
A couple of days ago VMware released version 6.5 Update 1 for some of their products:
I was waiting for Update 1 of the vSphere Stack for a while now, and the List of bugfixes has quite a few entries with critical bug fixes.
Today I attended a Web-Session from VMware with the topic vSAN troubleshooting tips and tricks and I wanted to share those tips and tricks with you.
Ensure that your hardware is on the VMware HCL
– Disks / Controllers / Firmare / Drivers
Ensure that you have up-to-date backups (and test the restore process fully)
One of my colleagues had a problem the other night. He was called to troubleshoot a VMware View environment which was not running as expected. One thing he did during the cleaning up was to get rid of a number of resource pools that were only created for the purpose of putting the VMs into “folders” when viewed from the old C# Client.
First off: This article is not sponsored by zerto in any way. I got to know zerto in-depth during a PoC we did for one of our customers and I fell in love with it. It’s so incredibly easy to use and has so many nice features. But let’s take it step-by-step.
If you are knee-deep in a troubleshooting session with a customer you want to be able to have some tools ready that do some tests for you. One of the things that in my case has happened quite a lot was that some network were connected but couldn’t communicate outside of the host. So in a HPE Blade Enclosure infrastructure this was most likely a forgotten VLAN tag in the server profiles.
In order to quickly eliminate this problem I have worked on a script that helps you test every network in your environment.
One of my customers called me up and told me that their VMware Fault-Tolerance (FT) VMs can no longer be backed up. The error it throws says: ” The operation is not supported on the object.”
When I looked at the recent task&events I was able to see that the backup was successful up to a point where someone reconfigured FT on that VM. So I went into the documentation (Link here) and saw that traditional VMware Snapshots are not supported on Fault Tolerance enabled VMs. There is a supported backup method for disk-only snapshots but that only works with the new FT (not legacy FT).
