This document:
provides a link to a Java program to allow network and disk red/write stats (as opposed to aggregate read+write stats - I think). However, not many details are presented therein, and I am curious if anyone has tried this "fix".
Q's:
1. What are the database space implications (CBM database - stats are dup'd) of running this fix? Does it balloon the space requirements for the CBM database? Or is the growth moderate/negligible? (From the text of the KB article, it seems like only separate read/write stats are added and not the rest of L3 stats...but I am not sure how much L3 normally adds, and how much(little) this fix adds in comparison).
2. "Reverting" this fix -why might we want to do this (eliminate DB growth?), and what happens to the CBM reports thereafter (I assume we lose the individual read/write stats after that and have only the aggregate? Other?)
3. I assume that we need to run this on each vCenter server? Or does running it on a single vC suffice (vCs are linked, if this makes any difference)?
Thanks in advance.