I only have 2 working hosts on this patch, 5 others are still on ESXi 5, 3086167. I have one ESXi6 3825889 that is currently unmanageable because the hostd service will not stay started. Apparently in 6.0u2 and this patch also have a bug in vSphere replication 6.1+. If you have a VM with multiple disks but you only replicate one (or some) of those disks, after some time whatever ESXi 6 host the VM is running on will crash hostd, and hostd will not start up until the machine is removed from the vmInventory.xml.
Panic: Assert Failed: "!repDiskInfo->GetDiskReplicationId().empty()" @ bora/vim/hostd/hbrsvc/ReplicationConfig.cpp:769
VMware QA at its finest...
Sorry to get a little off subject here, but the bottom line is, in my situation just do Instant Recovery to one of the 5 ESXi hosts still running 5.0, 3086167? Backups seem to be running fine for VM's on my two 6.0 machines.