After VMware released vSphere 6.7 Update 1 all want to install it. But many of them didn’t check the interoperatibility with, for example, the backup software. So… Veeam Backup and Replication 9.5 U3 not supports vSphere 6.7 Update 1.
The problem is in a small API change with big impact. There is a workaround for all of the early updaters to get your broken backups work again.
VMware reports an error where the tmpfs partition on NSX 6.3.6 and NSX 6.4.1 could run out of space. The file /run/vmware/vshield/cmdOut/ha.cid.Out grows up and fills the temporary file system completly.
After upgrading my production vCSA from 6.0 to 6.5 U1d, the “Scan for Updates” always runs in an unknown error. Before the upgrade everything works fine and the upgrade of the vCSA was easy to and finished without any error.
After some research and logfile analyzing I found two solutions.
In my previous posts I wrote about the upgrade of vCSA (vCenter Server Appliance) from version 5.5 to 6.0.
In all my lab testing the upgrade runs without any errors. On our production site I was doing the upgrade and the migration went fine until the new appliance boots for the first time.
The services start all until the vPostgres database starts. Something in the upgrade script gives back an error. Installation abort and I must boot the old vCSA 5.5.
VMware closed my call, because of an unsupported way getting vCenter Server for Windows to the vCSA 5.5. Everything runs in the vCSA 5.5. The upgrade fails and with the migrated database there is no support.