ccatlett1984 wrote:I will add this comment, the way averaging is computed, gives false data with the undersized/oversized vm reports.
Over-sized/under-sized reports are using buffers of 30% to address this, so that every performance spike (if it happens on regular basis) will be "accounted" in the recommendation.
michaelB wrote:Ok, I'll just try to explain what I'm doing with veeamONE actually.
We have a new VMware infrastructur with new Servers(ESXi hosts) and new datastores. The datastores have different performance features. The first half of them have a really good IOPS performance and average throughput. The other half is the opposite and have really good throughput performance and averagy IOPS. Now I'm analyzing with veeamONE which datastore is the best for each VM. It would be easy to say "store all database VMs to the first datastore and all like filetransfer VMs to the second", but our case is not that simple. Our VMs are performing differently and often they use their full ressources only for a short period of time(5min-2hours). Even if its a short period of time it is really important for us that the VMs get as much performance as they can get in this time.
Now, if I use veeamONE i need a long period of time (1-2 weeks) to fully analyze the VMs. For example, my threshold to choose one of the good perfoming IOPS datastores is >750 IOPS and the chart would show me it is more than one peak. VeeamONE tells me now for one VM "Datastore IO usage maximum 200 and multiple peaks at 200 IOPS - past week", so i would choose one of the other Datastores whith lower IO performance. But this information is simply wrong, cause in reality the peaks are about 1000 IOPS and I would choose the wrong Datastore.
Now luckily I know this behavior. Strangly if I analyze with a custom interval only the peak, it seems like I get the correct maximum value (>1000, 2 days ago). So the correct data seems to be stored but not to be shown in the past week view. I could now analyze each peak for a big amount of VMs and different performance types, but this would be really uncomfortable.
Veeam and VeeamONE is new for me and may be I'll get the informations which I need if I know more about the reporting features.
That's a perfect usage scenario for Veeam ONE. Automating VM placement or giving recommendations on where to put VM sounds like a good feature request. For your analysis I would also recommend to review our datastore performance assessment report that would correlate latency, IOPs and write/read rate over the historical time period.