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.
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.