To go along with the newly released VMware vCenter 6.7 Update 1 release, comes VMware ESXi 6.7 Update 1 as well.
As you might expect with an Update 1 release there are a number of patches, fixes and new additions with ESXi 6.7 U1. If you haven’t already seen, check out the release notes here.
Below are two ways to easily upgrade your ESXi 6.0-6.7 hosts to ESXi 6.7 U1 using the command line or by using VMware Update Manager.
VMware vCenter 6.7 U1 has recently been released. Last week I posted how to upgrade VCSA 6.7 to 6.7 Update 1, this post will walk you though upgrading VMware vCenter Server Appliance 6.5 to VCSA 6.7 Update 1!
When doing a VCSA version upgrade the upgrade process is much different, than going from say 6.7 to 6.7 U1. When going from 6.5 to 6.7 the upgrade is actually broken up into two stages.
The first stage involves deploying a brand new vCenter 6.7 appliance. Then the second stage will copy the data from your 6.5 VCSA into the newly deployed 6.7 VCSA from stage 1.
VMware has released vCenter Server 6.7 Update 1 and with comes with a number changes.
One most notable change is the feature complete HTML5 vSphere client. The vSphere client in vCenter 6.7 Update 1 now includes the ability to manage:
- Host profiles
- Auto deploy
- Full vSphere Update Manager (VUM)
- A new dark theme
- and vCenter High Availability.
That’s no where near all of the changes though, there are many more changes and updates in the 6.7 Update 1 update. Be sure to read the full release notes here.
In this post we’ll see just how easy it is to upgrade from VCSA 6.7 to VCSA 6.7 Update 1 in just a couple steps!
VMware released ESXi 6.7 a little while ago, but it’s only been here recently have I started deploying it in my home and work lab environments. Below are two ways to easily upgrade your ESXi 6.5 hosts to ESXi 6.7 using the command line or by using the VMware ESXi offline bundle.
The other day, one of our volumes in the lab environment filled up. This volume has a couple large VM’s on it, coupled with a couple different Veeam backup jobs running using the native Veeam backup methods as well as using NetApp snap mirror to snapshot the volume and then using Veeam to ship it out to Azure.
At any rate the volume filled up to the point where vCenter wasn’t allowing me to migrate VM’s off the datastore. I really didn’t want to expand the volume just so I could move VM’s off of it.
Instead, I decided to delete some of the older proof of concept snapshots from SnapMirror. Below are the quick and easy steps to clear up some un-used snapshots and free up some space on the datastore.
While moving some VM’s from Hyper-V to VMware using VMware Converter a VM failed to convert with the error: FAILED: The VSS snapshots cannot be stored.
FAILED: The VSS snapshots cannot be stored because there is not enough space on the source volumes or because the source machine does not have any NTFS volumes. Error code: 2147754783 (0x8004231F).
Come to find out the System Reserved partition was full. Our soon to be retired Appassure backup application was nice enough to fill up the volume.
Luckily Appassure is being replaced by Veeam and fixing the above VMware Converter error is an easy fix.