Yes, VMware will disable TPS by default @vSphere 5.1/5.5 from Q4 so that is a valid scenario for the future!http://blogs.vmware.com/apps/2014/10/di ... tions.html
Windows VMs running Windows 2008 and higher can hardly use TPS because the OS encryts the RAM content, so vSphere can't deduplicate the RAM content.
But we run VMs that have many similar (unecrypted) RAM pages, therefore rely heavily on TPS, but still wanted to see if we could optimize our VMs.
For our example - As you can see our VM is sized at 10GB Ram.
The vSphere overview shows us, that ~0,9GB is activly used (orange curve) / 1,7GB max. and ~3GB are shared with over VMs (purple curve).
So without TPS the VM would be using 1,7GB + 3GB = 4,7 GB Ram (active) I suppose.
But the standard veeam ONE report (igonring the shared RAM) would rather tell me to size the VM to 2,4GB Ram (= 1,7GB + 30%) - and that would be way too low, because the VM would have to be set to 4,7 GB at the very least (so that the OS can see the 4,7 GB, regardless if the hypervisor can share 3GB with other VMs through TPS).
So yes you should make a new report "Disabling TPS Host Memory Requirements" and
modify the default report that the recommended RAM size = active memory + shared memory
! Without that, the "oversized VM" reports / recommendations seem too dangerous to me.