vSphere 6 Update 1 - Veeam NFC storage connection is unavailable

vSphere 6 strikes again.

After an upgrade from vSphere 6 to vSphere 6 Update 1 all of our Veeam backups were failing with the message

"Processing VirtualMachineName Error: NFC storage connection is unavailable. Storage: [stg:datastore-42,nfchost:host-174,conn:vCenterServer]. Storage display name: [datastore]. Failed to create NFC download stream. NFC path....."

Here are a couple of write ups I found after the fact.  Had I known, I probably would have held off a few more weeks before upgrading.

http://triumphr3.blogspot.com/2015/09/vmware-6.html

http://www.vzaddict.com/updates/alert-veeam-customers-read-this-before-applying-vmware-vsphere-6-0-update-1/

https://www.veeam.com/kb2063

ESXi /var/log/hpHelper.log growing

As a follow up to my previous post (http://technotes.smoothwater.net/2015/10/ramdisk-var-is-full-and-vmotion-fails.html)

I found how to disable the HP Service that came in a custom ESXi image. We don't use the iLO connection between VMWare and iLO.  Here is a KB Article from VMWare.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2055924

ramdisk 'var' is full and vMotion Fails

I recently had a couple of odd events in a VM cluster.  I started looking one particular host and found the some odd entries in the Events tab in the vSphere Client.  Mostly it was

• The ramdisk 'var' is full.  As a result, the file /var/run/vmware/tickets/vmtck-<id> could not be written.

I couldn't find the particular error in VMWare KBs, but I found my problem in an article at Techazine.com

Here's an excerpt from that post.