View Only
  • 1.  Are these issues in previous versions resolved?

    Posted Sep 28, 2016 01:20 PM

    I had these questions posed to me by a service provider who is hesitant to upgrade. Currently they stopped using it after 3.3.2


    Does this version fix the problem in earlier versions that if a vCenter server is so busy or is rebooted for Windows Updates, etc., that a polling is missed, that the usage meter automatically reports double?

    The reporting metric was half of RESERVED memory, but I don’t reserve memory on any hosted system and I’ve been reporting half of the total assigned (and with what they are doing, active memory is even less than that for these systems). But when I used the Usage Meter before, it would report half assigned UNTIL it missed an interval, then jump to 100% of assigned.

  • 2.  RE: Are these issues in previous versions resolved?

    Posted Oct 04, 2016 12:40 AM

    You should not see any double billing or incorrect reporting of memory in 3.5