After upgrading vCenter 6.7 to vCenter 6.7 Update 1 in one of my environments, it was noticed that Veeam backups where failing with the error: Object reference not set to an instance of an object.
Error: Object reference not set to an instance of an object
I’m running Veeam Backup and Replication 9.5 U3a and after doing some digging around, it seems there is an API change in vSphere 6.7 Update 1 that is causing the backups to fail.
While Veeam plans to resolve this issue with their new Update 4 version coming out soon, there is a very simple work around thanks to this forum post.
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!
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.
VMware just released VMware vCenter 6.5 Update 1 just last month, in case you’ve missed it check out the release notes as there are a lot of fixes, improvements and additions.
In this post we’ll see just how easy it is to update the VMware VCSA. Before you do any VMware update I’d highly recommend checking out the VMware Interoperability Matrices to check compatibility of other VMware products. Once you’ve done that, lets begin!
VMware has announced that VMware vSphere 6.5 has gone general available this week. Now installing VMware vCenter Server Appliance 6.5 (VCSA) is even easier as the requirement for the client integration plugin has been removed and now the VCSA appliance is delivered via an ISO image with an installation wizard that’s been broken up into two stages.
The VCSA 6.5 ISO offers two types of installation methods, CLI and GUI install – both availalbe for Windows, Mac and Linux machines. In this guide I’ll walk through the steps of installing VCSA 6.5 using the Windows GUI install.
VMware has released vCenter Server 6.0 Update 2 and ESXi 6.0 Update 2 (build: 3620759) which include a number of new features and fixes. VMware has also released the much anticipate VSAN 6.2 which includes it’s own bunch of new features such as deduplication, compression, QoS, and RAID5/RAID6 Erasure coding.